APAR status
Closed as Permanent restriction.
Error description
Error Message: The customer had registered shutdown hooks and found that they had run - the JVM had closed down - on a Windows log off event. . Stack Trace: N/A . This problem is not seen with earlier service refreshes for all the releases. This is however not a regression.
Local fix
The -Xrs option can help ignore the log off event. However, with this option the shutdown event would also be ignored. It is not feasible to use this as a work-around if the application registers shutdown hooks with the JVM.
Problem summary
The JVM shut down on a CTRL_LOGOFF_EVENT because this event was translated into "termination" on the Windows platform - while this is valid for normal console based processes, non-interactive services should be allowed to survive across a Windows log off event.
Problem conclusion
This is considered as a permanent restriction in Java 5 and below releases. The user can apply the work around in Java 5. The issue is addressed in Java 6 and above releases through the APAR IV37554.
Temporary fix
Comments
APAR Information
APAR number
IV37555
Reported component name
JAVA 5 CLASS LI
Reported component ID
620500130
Reported release
500
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-03-04
Closed date
2013-10-08
Last modified date
2013-10-08
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 CLASS LI
Fixed component ID
620500130
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVQ3Y","label":"Java Class Libraries"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
08 October 2013