Kbase P12958: Sonic Adapter crashed after increasing the "maxClientInstance" with a java.lang.OutOfMemoryError
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/4/2006 |
|
Status: Verified
FACT(s) (Environment):
SonicMQ
Progress 9.1B
Progress 9.1C
Progress 9.1D
SYMPTOM(s):
SonicMQ 4GL adapter crashes
java.lang.OutOfMemoryError
JVM out of memory: Adapter emergency exit. Use the JVM's -mx, -ss and -oss startup parameters to increase the memory available for the adapter. (9363)
CHANGE:
Increased the "maxClientInstance" parameter of the Sonic Adapter to 80
CAUSE:
The amount of available memory for the Java process performing the task was not sufficient. The default limit is 16MB which is not always sufficient especially with large messages or an increased number of maxClientInstance. 16MB of available memory is not enough for 80 Client Instances working with messages inside the adapter with a normal processing application.
FIX:
The JVMARGS parameters "-Xmx" or "-mx" set the maximum Java heap size. Increase the maximum amount of memory that can be used for Progress Java Applications such as the SonicMQ Adapter.
(maximum Java heap size,-mx size) "-mx32m" tells to the JVM that the SonicMQ Adapter has 32 Mb heap allocated for the JVM.
For the SonicMQ Adapter on a windows environment perform the following:
1. Start REGEDIT
2. Select HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER, SOFTWARE, PSC, PROGRESS, 9.1X, JAVA
3 Select JVMARGS
4 Add the entry : -mx32m
5. The JVMARGS registry key should have a value of -ms8m -mx32m.
6. Restart the Adminserver
For the SonicMQ Adapter running in a unix environment perform the following: 1. Edit the $DLC/bin/properties/ubroker.properties file 2. Under [Adapter], jvmArgs=$JVMARGS 3. Change to [Adapter], JVMARGS="-ms8m -mx32m $JVMARGS" 4. Restart the Adminserver