IV02378: JAVA EXITS SILENTLY AND UNEXPECTEDLY ON LINUX DUE TO SIGPIPE

PM52003: SHIP SDK apar IV02378 as WSAS iFix
PM52089: SHIP SDK APAR IV02378 AS WSAS IFIX - WINDOWS
PM53783: SHIP several SDK apars as WSAS iFix on top of 1.6 SR9 FP2
PM52687: SHIP SDK APAR IV06580 and defect 184227 as WSAS IFIX

APAR status

• Closed as program error.

Error description

• Error Message: N/A
  .
  Stack Trace: N/A
  .
  SIGPIPE kills the java process on Java6 SR9 (and SR9FP1),
  whereas previous releases this signal is ignored.
  

Local fix

Problem summary

• The core issue is a combination of two APARs and a change
  pwgetuuid().
  APAR IZ86774 : Signal chaining does not work on Linux JDKs
  APAR IZ73232 : Signal chaining functionality issue
  Linux kernel reported against : 2.6.18-238.1.1.el5
  Upon SDK startup a call is made to pwgetuuid() before the SDK
  signal handlers are registered.  On newer versions of linux,
  getpwuid() registers a handler for SIGPIPE.  The SDK notices
  that a handler has already been registered for SIGPIPE, and as
  such, does not register the SIG_IGN handler for SIGPIPE,
  believing that the application has installed its own.
  

Problem conclusion

• This defect will be fixed in:
  6.0.0 SR9 FP3
  6.0.1 GA FP2
  5.0.0 SR13
  .
  The JVM has been updated to register the handler for SIGPIPE
  earlier in the startup sequence to avoid this situation from
  arising.
  .
  To obtain the fix:
  Install build 20110629 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:

  IV02379

Fix information

• Fixed component name

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels

• R600 PSY

     UP

• R260 PSY

     UP