APAR status
Closed as program error.
Error description
Error Message: N/A . Stack Trace: write () JVM_Write () ... .
Local fix
Problem summary
The JVM gets terminated due to the signal SIGXFSZ ( Signal 25 ) when the java file operations (like write) exceeds the file size limitation. The issue is only observed in Linux Operating System (OS). Since, the JVM was not enabled to handle the SIGXFSZ signal, the handling was performed by OS. As a result of this, the OS terminates the process causing JVM to crash.
Problem conclusion
This APAR will be fixed in the following Java Releases: 6 SR16 (6.0.16.0) 7 SR7 (7.0.7.0) 6 R1 SR8 (6.1.8.0) 7 R1 SR1 (7.1.1.0) . The JVM has been updated to handle the file system limitation condition by default from Java 7 Release 1 onwards. For Java 6, Java 626 and Java 7, the handling of Signal SIGXFSZ is not enabled by default, but it can be enabled with -XX:+HandleSIGXFSZ option.
Temporary fix
N/A
Comments
APAR Information
APAR number
IV53934
Reported component name
J9 COMMON CODE
Reported component ID
620700127
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-01-13
Closed date
2014-01-20
Last modified date
2014-04-30
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
R600 PSY
UP
R260 PSY
UP
R270 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVQ3W","label":"Virtual Machine"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
30 April 2014