Error returned from websphere server shown below when check_jmx runs. What causes this error? application configuration error?
$ /usr/local/nagios/libexec/check_jmx -U service:jmx:rmi:///jndi/rmi://AZWAPPJISCPS01.mfcgd.com:5190/jmxrmi -O java.lang:type=Threading -A ThreadCount -c 225
JMX CRITICAL - JVMVRFY027 receiver is incompatible with declaring class; class=javax/management/remote/rmi/RMIConnectionImpl$CombinedClassLoader, method=loadClass(Ljava/lang/String;Z)Ljava/lang/Class;, pc=203
Exception Details:
Location:
javax/management/remote/rmi/RMIConnectionImpl$CombinedClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class; @203: JBinvokevirtual
Reason:
Type 'java/lang/Object' (current frame, stack[2]) is not assignable to 'java/lang/Throwable'
Current Frame:
bci: @203
flags: { }
locals: { 'javax/management/remote/rmi/RMIConnectionImpl$CombinedClassLoader', 'java/lang/String', integer, integer, null, top, top, top, top, top, top, top, top, integer, 'java/lang/String', 'javax/management/remote/rmi/RMIConnectionImpl$CombinedClassLoader', 'java/lang/Exception', 'java/lang/Object' }
stack: { 'uninitialized', 'uninitialized', 'java/lang/Object' }
Exception Handler Table:
bci [150, 160] => handler: 163
bci [63, 92] => handler: 98
bci [5, 117] => handler: 117
bci [251, 254] => handler: 254
Stackmap Table:
full_frame(@46,{Object[#5],Object[#25],integer,integer,null,Object[#25],Object[#5]},{})
same_frame(@50)
same_locals_1_stack_item_frame(@51,integer)
same_locals_1_stack_item_frame(@54,integer)
full_frame(@95,{Object[#5],Object[#25],integer,integer,null,Object[#25],Object[#5],Object[#25],Object[#5],Object[#6],Object[#6]},{})
full_frame(@98,{Object[#5],Object[#25],integer,integer,null,Object[#25],Object[#5],Object[#25],Object[#5]},{Object[#16]})
append_frame(@100,Object[#28])
same_locals_1_stack_item_frame(@104,Object[#30])
chop_frame(@114,3)
full_frame(@117,{Object[#5],Object[#25],integer,integer,null},{Object[#16]})
full_frame(@134,{Object[#5],Object[#25],integer,integer,null,top,top,top,top,top,top,top,Object[#16]},{})
full_frame(@136,{Object[#5],Object[#25],integer,integer,null},{})
full_frame(@163,{Object[#5],Object[#25],integer,integer,null,top,top,top,top,top,top,top,top,integer,Object[#25],Object[#5]},{Object[#24]})
append_frame(@169,Object[#24],Object[#28])
same_frame(@197)
same_locals_1_stack_item_frame(@211,Object[#36])
same_frame(@212)
chop_frame(@222,2)
full_frame(@241,{Object[#5],Object[#25],integer,integer,null,top,top,top,top,top,top,top,top,integer,Object[#25],Object[#5],Object[#30]},{Object[#30]})
full_frame(@251,{Object[#5],Object[#25],integer,integer,Object[#30],top,top,top,top,top,top,top,top,integer,Object[#25],Object[#5],Object[#30]},{})
same_locals_1_stack_item_frame(@254,Object[#16])
full_frame(@271,{Object[#5],Object[#25],integer,integer,Object[#30],top,top,top,top,top,top,top,Object[#16],integer,Object[#25],Object[#5],Object[#30]},{})
JMX monitoring error
Re: JMX monitoring error
There appear to be some comments about similar things on that plugin's page:
https://exchange.nagios.org/directory/P ... mx/details
You might have a look at that, and try those suggestions.
--Jeffrey
https://exchange.nagios.org/directory/P ... mx/details
You might have a look at that, and try those suggestions.
--Jeffrey
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!