IV20688: FLOATING POINT ERROR WITH -XCEEHDLR
Closed as program error.
Error Message: Unhandled exception Type=Floating point error vmState=0x00040001 J9Generic_Signal_Number=00000020 Condition_Facilty_ID=CEE Condition_Message_Number=0C89 Condition_Severity=0003 Handler1=193D1500 Handler2=193DE1E0 . Stack Trace: N/A . Condition_Message_Number in range 0x0C88 (3208) to 0x0C82 (3234) inclusive. This range of Condition_Message_Number corresponds to LE conditions CEE3208S to CEE3234S (inclusive).
Disable concurrent GC, for example, by using the command-line option -Xgcpolicy:optthruput
The problem is caused when JNI native code triggers an LE condition in the range CEE3208S to CEE3234S (inclusive), which are considered to be "arithmetic" LE conditions. When the JVM command-line option -XCEEHDLR is present, the JVM should convert arithmetic LE conditions that occur in JNI native code to Java exceptions of type com.ibm.le.conditionhandling.ConditionException. The problem is that the arithmetic condition is not being converted to a Java exception, and instead, the LE condition is being treated as a regular crash. The JVM therefore generates diagnostics and terminates the process. Note that this is an intermittent issue and only occurs when a thread doing garbage collection (GC) work examines the resources owned by the thread that triggered the arithmetic LE condition
This defect will be fixed in: 7.0.0 SR1 6.0.1 SR2 . The JVM has been updated such that threads doing work for the GC no longer interfere with the JVM's ability to detect that the arithmetic LE condition occurred in a JNI native.
Reported component name
J9 COMMON CODE
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
J9 COMMON CODE
Fixed component ID
Applicable component levels