Problem description: Download the electronic report. When the electronic report is too large, "root cause
Servletexception java. Lang. outofmemoryerror"
Problem status: resolved
Solution: Adjust the commenv parameters in BEA, WebLogic, and common.
: Sun
If "% production_mode %" = "true" Goto sun_prod_mode
Set java_vm =-Client
Set mem_args =-xms256m-xmx512m-XX: maxpermsize = 256 m
Set java_options = % java_options %-xverify: None
Goto continue
: Sun_prod_mode
Set java_vm =-Server
Set mem_args =-xms256m-xmx512m-XX: maxpermsize = 256 m
Goto continue
Solve this problem
Reference:
Maxpermsize:
The permanent space is memory allocated outside the regular
Heap (I. e. In addition to the-xmx setting), so it is important
To ensure there is enough physical RAM on the machine.
The permanent space is used to primarily store classes and
Objects Created for reflection support (methods etc.). If
You have a large number of classes in a Java application,
An OOM can occur if the permsize is too small.
From one of your previous posts, you seem to have 8 applications,
So yes, setting the permsize and/or maxpermsize cocould help.
Also, 256 MB sounds small for a server with 8 applications.
The OOM cocould simply indicate that your heap is too small.
Hope this helps,
Arunabh