APAR status
Closed as program error.
Error description
Error Message: JVMJNCK038E JNI error in CallObjectMethod/CallObjectMethodV: Argument #2 (0x000000011153C788) is not a valid object reference. It's type is: unknown JVMJNCK080E Error detected in the outermost frame of an attached thread JVMJNCK024E JNI error detected. Aborting. JVMJNCK025I Use -Xcheck:jni:nonfatal to continue running when errors are detected. Fatal error: JNI error . Stack Trace: N/A . The issue only occurs when pushing and popping local frames, this is specifically an issue with JNI Check Pedantic and does not cause the application to behave incorrectly.
Local fix
Do not use pedantic mode for JNI Check
Problem summary
The problem is caused by JNI Check pedantic not walking all the frames in a stack when checking a local reference is valid after PushLocalFrame()/PopLocalFrame() have been used.
Problem conclusion
This defect will be fixed in: 7.0.0 SR5 6.0.1 SR6 6.0.0 SR14 . The JVM has been updated to walk all the frames of a stack when checking for a valid local reference in JNI Check Pedantic mode
Temporary fix
Comments
APAR Information
APAR number
IV38614
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
2013-03-25
Closed date
2013-03-25
Last modified date
2013-03-25
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
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