Exception Signal 11 while starting Java probe with the WebSphere

Immediately upon starting the WebSphere application server with Diagnostics Probe, the JVM crashes. In the dump file from the crash, if "Exception Signal 11" is observed in WebSphere logs.

E.g.

JVMDG217: Dump Handler is Processing Signal 11 – Please Wait.

JVMDG303: JVM Requesting Java core file

JVMDG304: Java core file written to /opt/WebSphere/AppServer/javacore.20101129.161814.22608.txt

JVMDG215: Dump Handler has Processed Exception Signal 11.

"signal 11 received" is seen in java core dump logs too.

Process level CPU usage metrics are not supported in probe for Linux 1.4.2 core, and though the probe should detect this initially, in some cases this didn’t happen.

Comment out the following metrics in etc/metrics.config file and restart the application/probe again:

ProcessMetrics/processCpuUtil=ProcessCpuUtil|percent|Probe

ProcessMetrics/processCpuUtilAbs = ProcessCpuUtilAbs|percent|Probe

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s