Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

How to resolve JNI Warnings in application logs

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:

Version history
Revision #:
2 of 2
Last update:
‎07-11-2017 03:21 PM
Updated by:
 
Labels (1)
Contributors


Found this article helpful? Click the Thumbs Up button.
Have a comment? Post it below.
0 Kudos