Java. Lang. outofmemoryerror: permgen Space

<Error> -Appname: 'leleapp', name: 'console', context-path: '/console'] root cause of servletexception.

Java. Lang. outofmemoryerror: permgen Space
>
#### <2009-5-9 11:38:07 P.M. CST> <error> <kernel> <localhost. localdomain> <esbserver> <[active] executethread: '0' for queue: 'weblogic. kernel. default (Self-tuning) '> <WLS kernel> <1241883487493> <BEA-000802> <ExecuteRequest failed

Java. Lang. outofmemoryerror: permgen space.
Java. Lang. outofmemoryerror: permgen Space
Error description:
Permgen space stands for permanent generation space, which is the permanent storage area of the memory. This part is used to store class and meta information. When the class is loaded, it is placed in the permgen space area. It is different from the heap area where the instance is stored. GC (garbage collection) permgen space is not cleared during the main program running period. Therefore, if the app loads many classes, the permgen space error may occur.

Solution:
Reference solution:

• 1. Increase maxperm size
• Eg:-XX: + maxpermsize = 256 m
• 2. These additional parameters may also be helpful in some cases.
• Eg:-xmn1228m-XX: + aggressiveheap-xms2048m-xmx2048m
• 3. Enable jvm gc logging to analyze the issue if problem still persists by setting following Parameter
• Eg:-verbose: GC-XX: + printgcdetails
• 
  

My solution: You can set setdomainenv. Sh in WebLogic:

Parameter mem_args = "-xms512m-xmx512m-XX: maxpermsize = 512 M"

Finally, the solution is successfully solved !!

Where-XX: + aggressiveheap:
Enables the JVM to automatically optimize various parameters based on the machine memory and the number of cpus. Generally, the maximum physical memory of the machine is used.
Hs_err_pid23131.log is also generated.
Note: Java applications may sometimes crash for various reasons. At this time, an error log similar to java_errorpid.log will be generated.
The following information is found in the log:
Pspermgen total 65536 K, used 65535 K [0x6e0c0000, 0x720c0000, 0x720c0000)
Object Space 65536 K, 99% used [0x6e0c0000, 0x720bffc0, 0x720c0000)
The above information shows that the JVM's permsize space is almost exhausted during crash. Therefore, we recommend that you increase the values of permsize and maxpermsize.