PM06896: SIGNAL 11 CRASH IN GC
Closed as program error.
Error Message: Signal 11 Crash in GC with -Xgcpolicy:optavgpause because of objects being wrongly collected (java heap corruption). . Stack Trace: The problem can manifest in many different places. The most common functions the crash can be seen are, fastLocalMark() localMark() . Using st_verify_heap tracing it can be checked if java heap corruption is happening or not.
If -Xgcpolicy:optavgpause is not used, problem will not happen.
Because of some bug in concurrent marking code, few objects were not marked as live and those objects were wrongly collected by GC.
This defect will be fixed in: 1.4.2 SR13 FP4 . The fix for this is to correct the bug in concurrent marking code to mark all the live objects correctly. . To obtain the fix: Install build 20100206 or later
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
Translate this page: