Kbase P96997: java.lang.OutOfMemoryError <<no stack trace available>> using newer version of Java.
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  07/10/2008 |
|
Status: Verified
SYMPTOM(s):
java.lang.OutOfMemoryError <<no stack trace available>> using newer version of Java
Installing Fathom upgrade.
java.lang.OutOfMemoryError <<no stack trace available>>.
FACT(s) (Environment):
Admnsrv.log message says Fathom upgrade completed.
Fathom Management
UNIX
CHANGE:
Changed from Java 1.3.0 to Java 1.3.1 on new host.
CAUSE:
Using default entries for JVMARGS in proenv which are not set high enough to accommodate the Java memory resources required.
FIX:
Edit the Progress/bin/java_env file JVMARGS parameter and increase the -Xms and the-Xmx parameters so they are large enough to accommodate the java memory resources requested. These settings are used for the Progress session in setting up the Java Environment.
The -Xms<size> sets the initial Java heap size, and the-Xmx<size> sets the maximum Java heap size.
Ensure there is enough available memory and swap space before increasing these parameter values.
To edit the java_env file, do the following:
Make a backup copy of the $DLC/bin/java_env file.
Open $DLC/bin/java_env in a text editor.
Move to the section of the java_env file specific to the OS platform involved (For
example, on Linux, move to the Linux section.)
Change the JVMARGS= line by adding new values and appending ${JVMARGS}.
For example, change JVMARGS="-ms8m" to JVMARGS="-Xms128m Xmx512 ${JVMARGS}"
Save and close the file.