APAR status
Closed as program error.
Error description
Error Message: Unhandled exceptionType=Segmentation error vmState=0x00020002J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000001Handler1=00007FA282A4FDB0 Handler2=00007FA2823975D0 InaccessibleAddress=0000000000000000RDI=00007FA27C03D400 RSI=00007FA27C3B7EB0 RAX=0000000000000000 RBX=00007FA249919610RCX=00007FA283B08998 RDX=0000000099669966 R8=00007FA283B08998 R9=00007FA2499198B0R10=00007FA27C284000 R11=0000000000000000 R12=00007FA28087F8C0 R13=0000000000000000R14=0000000000000000 R15=0000000000000002RIP=00007FA28059F571 GS=0000 FS=0000 RSP=00007FA2499194F0EFlags=0000000000210246 CS=0033 RBP=00007FA2280059C8 ERR=0000000000000004TRAPNO=000000000000000E OLDMASK=0000000000000000 CR2=0000000000000000xmm0 00007fa283b08a00 (f: 2209384960.000000, d: 6.933518e-310)xmm1 0000000000000010 (f: 16.000000, d: 7.905050e-323)xmm2 0000000000010001 (f: 65537.000000, d: 3.237958e-319)xmm3 00007fa27c280f00 (f: 2083000064.000000, d: 6.933512e-310)xmm4 00007fa2499199f0 (f: 1234278912.000000, d: 6.933470e-310)xmm5 00007fa24ac74866 (f: 1254574208.000000, d: 6.933471e-310)xmm6 00007fa2499199f0 (f: 1234278912.000000, d: 6.933470e-310)xmm7 0000000000000008 (f: 8.000000, d: 3.952525e-323)xmm8 402e22f5a0b1b980 (f: 2696002048.000000, d: 1.506828e+01)xmm9 3ff0000000000000 (f: 0.000000, d: 1.000000e+00)xmm10 3ec1000000000000 (f: 0.000000, d: 2.026558e-06)xmm11 3d75474c359916f1 (f: 899225344.000000, d: 1.209543e-12)xmm12 3ec45f484c480625 (f: 1279788544.000000, d: 2.428555e-06)xmm13 bbf3a2b49db2a368 (f: 2645730048.000000, d: -6.652789e-20)xmm14 402e7f9c1e980d00 (f: 513281280.000000, d: 1.524924e+01)xmm15 0000000000000000 (f: 0.000000, d: 0.000000e+00)Module=/bluebird/builds/bld_212885/sdk/xa6480/jre/l ib/amd64/default/libj9gc28.soModule_base_address=00007FA2803AC00 0Target=2_80_20140912_212885 (Linux 2.6.32-431.17.1.el6.x86_64)CPU=amd64 (2 logical CPUs) (0x1675b0000 RAM) . Stack Trace: N/A .
Local fix
This issue only occurs if the JIT is in use, so -Xint will work around it.
Problem summary
The JVM misinterprets the exception handler location if -Xdump:events=catch triggers in a JIT compiled exception handler.
Problem conclusion
The JVM has been updated to use the correct location. . This APAR will be fixed in the following Java Releases: 6 R1 SR8 FP3 (6.1.8.3) 7 R1 SR2 FP10 (7.1.2.10) 6 SR16 FP3 (6.0.16.3) 7 SR8 FP10 (7.0.8.10) . Contact your IBM Product's Service Team for these Service Refreshes and Fix Packs. For those running stand-alone, information about the Service Refreshes and Fix Packs can be found at: https://www.ibm.com/developerworks/java/jdk/
Temporary fix
Comments
APAR Information
APAR number
IV67820
Reported component name
J9 COMMON CODE
Reported component ID
620700127
Reported release
260
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-12-11
Closed date
2014-12-11
Last modified date
2014-12-11
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
R260 PSY
UP
R270 PSY
UP
R600 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":"6.1","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
21 February 2022