a "signal 11" problem this happens once a day on WAS 5.1/AIX 5.2

Discussions

Performance and scalability: a "signal 11" problem this happens once a day on WAS 5.1/AIX 5.2

  1. We have an application running on IBM WAS 5.1 (Sun JVM 1.4) on AIX5.2 and once a day we get this error ...any idea what this error is ?

    thanks

    SN
  2. First, I was not aware the you could replace the IBM JVM with Sun's JVM. Was that a typographical error?

    A signal 11 (SIGSEGV) is a memory access problem. Are any of your applications using JNI? Doesn't the SIGSEGV error message tell you the specific module? In addition to the JVM logs (SystemOut.log, SystemErr.log), look at the process logs (native_stdout.log, native_stderr.log).

    Bill Lasley
    Versant Corp.
    http://www.versant.com
  3. opps...sorry typo error..is there a way i could resolve this issue ?
  4. You can't resolve it until you find out what is causing it. Look in the logs for a clue: SystemOut.log, SystemErr.log, native_stdout.log, and native_stderr.log. The SIGSEGV message may point you to the specific module that has the memory access problem. Using that knowledge you may be able to deduce where the problem is occurring, and from that knowledge determine the root cause. I would be surprised if this is a WebSphere problem. Do any of the applications running in the JVM use JNI to call non-Java program?

    Bill Lasley
    Versant Corp.
    http://www.versant.com
  5. yes it does....why you think that might be the one causing it ?
  6. You can't resolve it until you find out what is causing it. Look in the logs for a clue: SystemOut.log, SystemErr.log, native_stdout.log, and native_stderr.log. The SIGSEGV message may point you to the specific module that has the memory access problem. Using that knowledge you may be able to deduce where the problem is occurring, and from that knowledge determine the root cause. I would be surprised if this is a WebSphere problem. Do any of the applications running in the JVM use JNI to call non-Java program? Bill LasleyVersant Corp.http://www.versant.com

    I think that the problem is with a JNI call to non-Java. Check the JDBC drivers. If you are using type-II drivers or least, they involve both Java source code (in the .jar libraries) and C code in the .so files. Most of the time, SIGSEGV errors only appear with code in .so libraries.


    Jose Ramon Huerga
    http://www.terra.es/personal/jrhuerga