* Exception in thread “CompilerThread1″ java.lang.OutOfMemoryError: requested 793020 bytes for Chunk::new. Out of swap space?
Out of memory while reading in symbol table of /apps/bea/weblogic92/jdk184.108.40.206/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl
( 0) 0xc8461230 [/apps/bea/weblogic92/jdk220.127.116.11/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 1) 0xc80a5fec [/apps/bea/weblogic92/jdk18.104.22.168/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 2) 0xc7f00420 [/apps/bea/weblogic92/jdk22.214.171.124/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 3) 0xc7f00ca0 [/apps/bea/weblogic92/jdk126.96.36.199/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 4) 0xc8368d08 [/apps/bea/weblogic92/jdk188.8.131.52/opt/java1.5/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 5) 0xc005b2e4 __pthread_body + 0x44 [/usr/lib/libpthread.1]
( 6) 0xc0065574 __pthread_start + 0x14 [/usr/lib/libpthread.1]
Java out of memory messages are marked with pid: 13828 in /var/adm/syslog/syslog.log.
– not enough swap space left, or
– kernel parameter MAXDSIZ is very small.
Although it appears that an OutOfMemoryError is thrown this apparent exception is reported by the HotSpot VM code when an allocation from the native heap failed and the native heap may be close to exhaustion. The message indicates the size (in bytes) of the request that failed and also indicates what the memory is required for. In some cases the reason will be shown but in most cases the reason will be the name of a source module reporting the allocation failure. If an OutOfMemoryError with this error is thrown it may require using utilities on the operating system to diagnose the issue further. Examples of issues that may not be related to the application are when the operating system is configured with insufficient swap space, or when there is another process on the system that is consuming all memory resources. If neither of these issues is the cause then it is possible that the application is failed due to native leak; for example, application or library code is continuously allocating memory but is not releasing it to the operating system.
For more information: http://java.sun.com/j2se/1.5/pdf/jdk50_ts_guide.pdf
The recommendation for swap space size in the Solaris is that swap should be configured about 30% of physical RAM.
The following link has suggested a workaround to add ‘-XX:+UseDefaultStackSize -Xss256K’ parameter.
Add: -XX:CodeCacheMinimumFreeSpace=2M -XX:+ReservedCodeCacheSize=64M -XX:PermSize=128m -XX:MaxPermSize=384m (As per your other JVM settings)
Sun team needs to be involved for this issue. Usually such issues are solved by sun support.
* java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
1) Set kernel parameter maxdsiz to a higher value
2) Reduce the current heap size.
3) Check the kernel values: ulimit -a
4) If the NPROC soft limit is lower than the hard limit, increase it as needed: ulimit -u <new value>.
Check the Operating System documentation to make changes permanent at the OS configuration files.
5) Need to reduce the JVM stack size and the OS stack size both. Set the -xss in java options and set ulimit -s on the OS level.
* java.lang.OutOfMemoryError: PermGen space
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.lang.Class.getConstructor0(Unknown Source)
at java.lang.Class.getConstructor(Unknown Source)
Solution: Increase the max permgen space -XX:MaxPermSize=256m
There can be a leak in the permgen objects. If tuning parameters do not resolve the issue, we need to use the memory leak detector tools and find out which instances in the permgen space are not getting cleared.
* java.lang.OutOfMemoryError: allocLargeObjectOrArray – Object size: 372032, Num elements: 372012
* java.lang.outofmemoryerror: nativeGetNewTLA
Solution: -XXtlasize:128k -XXlargeobjectlimit:128k
If this does not solve the issue, we need to check in the application code for the large objects being created and not being destroyed. Take JRA Recording (Oracle JRockit) or use JConsole and memory leak detector tools (JMAP, JHAT) for analysis on the
* java.lang.OutOfMemoryError: Java Heap Space
Solution: First thing that needs to be checked is the gc logs. Need to check whether the garbage collection is happening properly. If the heap keeps gradually increasing even after full gc, tune the gc algorithms and check if the behavior is the same. Use memory leak detector tools for both sun jdk and JRockit to check which instances from the application are not getting destroyed.
If this is not the case and the application genuinely needs more memory, increase the heap size by using the parameters:
Example: -Xms2048m -Xmx2048m
Solution: Stack over flow error is usually generated due to a recursive call made by the application (infinite recursion), or its because of an attempt to allocate more memory on the stack than will fit. This is usually the result of creating local array variables that are far too large for the current stack.
For the first possibility, we need to check the application code as to where is the recursive call being made.
For the second possibility, we can increase the JVM stack size by the parameter : Example: -Xss512K
If you have any queries regarding the out of memory errors, please do get back to us.