How to resolve JNI Warnings in application logs

[#1]

Problem:

Users find JNI-related warning messages in application logs. 

Example:

WARNING: JNI local refs: 76306, exceeds capacity: 32 
at sun.instrument.InstrumentationImpl.getAllLoadedClasses0(Native Method) 
at sun.instrument.InstrumentationImpl.getAllLoadedClasses(InstrumentationImpl.java:176) 
at com.singularity.ee.agent.appagent.services.bciengine.B.a(B.java:135) 
at com.singularity.ee.agent.appagent.services.bciengine.B.b(B.java:194) 
at com.singularity.ee.agent.appagent.services.bciengine.B.c(B.java:268) 
at com.singularity.ee.agent.appagent.services.bciengine.asm501.B.a(B.java:1003) 
at com.singularity.ee.agent.appagent.services.bciengine.asm501.B.c(B.java:976) 
at com.singularity.ee.agent.appagent.services.bciengine.asm501.B.a(B.java:56) 
at com.singularity.ee.agent.appagent.services.bciengine.asm501.H.a(H.java:156) 
at com.singularity.ee.agent.appagent.services.bciengine.asm501.B.a(B.java:632) 
at com.singularity.ee.agent.appagent.services.bciengine.asm501.B.a(B.java:860) 

Solution:

1. Restart the JVM without the Xcheck:jni parameter 

or

2. Change the JVM to JDK 8u65 or 8u60 


Related Links:

• JDK bug system: Excessive checked JNI warnings from Java startup
• JDK bug system: -Xcheck:jni improvements to exception checking and excessive local refs