Troubleshooting JMX Monitors:
I would like to clarify this manual is how to troubleshot a JMX monitor not how to configure it, to know if the JMX monitor can run in SiteScope and what we can do with it.
There are a lot of manuals how to configure a JMX monitor in SiteScope, for example, in SiteScope Monitor Reference.pdf on chapter 37 explain the SiteScope limitations, and the versions can SiteScope monitor.
WebLogic 9.x, 10.0, 10.3, 11g (10.3.1-10.3.5)
Apache Tomcat 5.0, 5.5, 6.0, 6.0.33, 7.0.25
Oracle Application Server 10.1.3g
JBoss servers 4.0.3, 4.2, 5.0, 5.1, 6.0, 6.1, 7.0
Sun Glassfish Enterprise Server 2.1, 3.1
A very important thing is the URL we use to connect to whose servers:
For Weblogic 9.x, 10.0x 10.3 or 11g:
For T3 Protocol:
For t3s Protocol:
For iiop Protocol:
For iiops Protocol:
But there are an easy workaround to know if it’s SiteScope or our JMX monitor who is refusing the connection. JConsole is our tool.
How to use Jconsole to connect to our JMX Server? Well there are different options. But the recommended one is to open a console and run the follow sentence:
jconsole -J-Djava.class.path=C:\SiteScope\java\lib\jconsole.jar;C:\SiteScope\java\lib\tools.jar;C:\SiteScope\WEB-INF\lib\wlfullclient.jar -J-Dcom.sun.CORBA.transport.ORBTCPReadTimeouts="1:60000:300:1"
Note: We must to use the same JAVA who uses SiteScope. We do not must to use OUR java. Why? Because SiteScope uses his own java to create the connections, if we use another java version it’s possible to be a different version with his singularities different from SiteScope Java. You can found SiteScope Java version on <SiteScope_Root>\java\bin, also you can found jconsole.exe in <SiteScope_Root>\Java\bin.
Let’s take a look into this sentence:
Jconsole à with this sentence we say to the system, open Jconsole
Djava.class.path=C:\SiteScope\java\lib\jconsole.jar;C:\SiteScope\java\lib\tools.jar;C:\SiteScope\WEB-INF\lib\wlfullclient.jar à with this sentence we specify the .jar files important and the certificates we will use to connect to our server
Dcom.sun.CORBA.transport.ORBTCPReadTimeouts="1:60000:300:1" àwith this sentence we specify the timeouts.
That will open a new window with SiteScope Jconsole, and now we must only to specify our URL to connect to the server, and the username and password.
Another typical problem can be the usernames and the passwords, it’s possible the username and the password we use to connect do not have enough rights to get the data we like. With this tool is a good way to check if the values that appear in SiteScope like N/A are because we cannot get counters from JConsole.