IZ06529: SIGABRT HANDLER RELIES ON THREAD BEING ATTACHED TO THE VM

APAR status

• Closed as program error.

Error description

• Error Message: "kill -ABRT" does not activate the dump agents.
  As a result, no javacore or Snap diagnostic files are generated,
  although, the OS may generate a core file on it's own.
  Instead, the following ouput is generated:
  "Abort (core dumped)"
  .
  Stack Trace: N/A
  .
  N/A
  

Local fix

• The user dump agent still works fine, so the workaround would be
  to add -Xdump options so that the same diagnostic files are
  created in reaction to injecting a SIGQUIT as would be generated
  by injecting a SIGABRT.
  Specifically, add the following -Xdump options to the
  commandline: "-Xdump:system:events=user
  -Xdump:snap:events=user".
  To activate this dump agent, issue the following: "kill -QUIT
  <pid>"
  

Problem summary

• This problem is caused by the SIGABRT signal handler (that is
  installed by the J9 VM) being invoked by the OS on a thread that
  was not attached to the VM.
  

Problem conclusion

• This defect will be fixed in:
  5.0.0 SR7
  .
  The J9 VM SIGABRT signal handler has been updated to explicitly
  attach the thread it is being invoked on to the VM, if it wasn't
  attached already.
  .
  To obtain the fix:
  Install build 20071018 or later
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  JAVA 5 J9 COMMO

• Fixed component ID

  620500127

Applicable component levels

• R500 PSN

     UP