APAR status
Closed as program error.
Error description
Error Message: The shutdown sequence dependent on SIGUSR2 does not execute. . Stack Trace: N/A . https://github.com/eclipse/openj9/issues/7749
Local fix
Problem summary
Currently, IBM J9 unblocks all supported signals during startup. A signal is unblocked even when a signal handler is not installed for it. This causes a conflict when a native application blocks a set of signals before invoking JNI_CreateJavaVM. In IBM J9, JNI_CreateJavaVM unblocks those signals at startup. This hinders the native application's signal handling behavior.
Problem conclusion
IBM J9 has been updated to unblock a signal only if a signal is used by the JVM i.e. a signal handler is registered for it. . This APAR will be fixed in the following Java Releases: 8 SR6 FP5 (8.0.6.5) . Contact your IBM Product's Service Team for these Service Refreshes and Fix Packs. For those running stand-alone, information about the available Service Refreshes and Fix Packs can be found at: https://www.ibm.com/developerworks/java/jdk/
Temporary fix
Comments
APAR Information
APAR number
IJ21098
Reported component name
J9 COMMON CODE
Reported component ID
620700127
Reported release
270
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-11-20
Closed date
2019-11-26
Last modified date
2019-11-26
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
J9 COMMON CODE
Fixed component ID
620700127
Applicable component levels
R270 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
21 February 2022