The following is a summary after a Java. Lang. outofmemoryerror: direct buffer memory error occurred

Causes:

It is used for NiO, but the direct buffer is not enough

Solutions

1) Check whether NiO is used directly or indirectly, such as manually calling the buffer generation method or using NiO containers such as netty, jetty, Tomcat, etc

2) – XX: maxdirectmemorysize is increased. The default value of this parameter is 64M, which can be increased according to the demand

3) Check if there is – XX: + disableexplicit GC in the JVM parameter, and remove it if there is

Code tracking:

When the ByteBuffer is generated, the allocation method is called. You can see system. GC ():

Similar Posts:

• [Solved] CDH6.3.2 Hive on spark Error: is running beyond physical memory limits
• eclipse.ini/myeclipse.ini -Xms，-Xmx，-PerSize
• Image has dependent child images [How to Solve]
• _DEBUGGER _03 _Server Tomcat v8.0 Server at localhost was unable to start within xx seconds
• Eclipse failed to create the java virtual machine [How to Solve]
• [Solved] fluentd Log Error: read timeout reached
• Tuning and setting of memory and CPU on yarn cluster
• JAVA package Run Error: Java hotspot (TM) 64 bit server VI warning: Info: OST; The ‘eror’ page file is too small to complete the operation
• Using join buffer (Block Nested Loop)
• MYSQL Error: Out of sort memory, consider increasing server sort buffer size; nested exception is java.sql.SQLException: Out of sort memory, consider increasing server sort buffer size