For releases of WebSphere Application Server v4.0:
- Add the following Java™ virtual machine (JVM™) argument.
- For Application Servers:
- In the Administrative Console, select the JVM settings tab of
the Application Server.
- Select Advanced JVM settings > Command line arguments.
- Add the following argument:
-XX:+PrintCompilation
- Restart the JVM for the change to take effect.
- For Administrative Server:
- Open the file,
install_root\bin\admin.configuration.
- On the line,
com.ibm.ejs.sm.util.process.Nanny.adminServerJvmArgs
add the following argument:
-XX:+PrintCompilation
- Restart the JVM for the change to take effect.
For releases of WebSphere Application Server v5:
- In the Administrative Console, navigate to Servers >
Application Servers > server_name.
- In the Additional Properties section, select Process
Definition > Java Virtual Machine > Generic JVM arguments.
- Add the following JVM argument:
-XX:+PrintCompilation
- Restart the JVM for the change to take effect.
Note: PrintCompilation writes to the
native_stdout (for v5)
and
stdout (for v4) file for the JVM, indicating the class and
method that are being HotSpot compiled. Identifying the method compiled
before the crash occurs is often helpful in providing a workaround to
stabilize the JVM.
Example of PrintCompilation output:
java.lang.String::<init> (157 bytes)
java.lang.String::hashCode (60 bytes)
java.util.jar.Attributes::read (256 bytes)
com.ibm.sslite.e::a (691 bytes)
com.ibm.sslite.h::c (428 bytes)
An unexpected exception has been
detected in native code outside the
. Unexpected Signal : 11 occurred at PC=0xff330924
Function name=memcpy
Library=/usr/platform/SUNW,Ultra-80/lib/libc_psr.so.1