APAR status
Closed as program error.
Error description
Error Message: Multiple threads stuck in parked state . Stack Trace: N/A .
Local fix
Problem summary
the problem occurs when the Java code depends on volatile semantics to ensure that the volatile field updates are seen in different threads. The problem is caused by incorrect volatile field handling. A memory fence for a volatile field is missing after a write operation due to incorrect JIT patching
Problem conclusion
This defect will be fixed in: 6.0.0 SR11 . The JVM has been updated to not patch over the fence if the field is found to be a volatile.
Temporary fix
Comments
APAR Information
APAR number
IV26340
Reported component name
JIT
Reported component ID
620700124
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-16
Closed date
2012-08-16
Last modified date
2012-08-16
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
JIT
Fixed component ID
620700124
Applicable component levels
R600 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC9HBA","label":"Just In Time (JIT) Compiler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
16 August 2012