Re: Sitescope JMX monitor error 31008 (1983 Views)
Reply
Frequent Advisor
Richard Snader
Posts: 56
Registered: ‎09-08-2003
Message 1 of 4 (2,083 Views)
Accepted Solution

Sitescope JMX monitor error 31008

We are trying to set up a jmx monitor against one of our servers running thrid party java apps.  Since I'm not by anymeans a Java guru, I'm lost as to how to get this resolved.  We can get to the jmx-console on port 10008, and it brings up the JBOSS console.  when we try to use the JMX Monitor on the same port, we get the 31008 error.  I've tried a bunch of ports that I see being defined in the process list, and I get one of two errors for each one that I try.  the errors I get are:

Error 31008
Error getting counters :
Error receiving browse data: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: ui01.gold01.uiq.bgesg.net; nested exception is:
java.net.ConnectException: Connection refused]


Error 31008
Error getting counters :
Error receiving browse data: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint]

 

 

Does anyone out there know how to read this process line and tell me if the right pieces are runinng for me to connect to this application, and if not what it is I need to ask the third part vendor to add?

 

 

root 6868 1 0 Oct26 ? 00:56:20 /usr/ssn/thirdparty/CURRENT/ssn_home/ssnjdk/jdk/bin/java -server -server -Xms1g -Xmx1g -XX:NewRatio=9 -XX:MaxPermSize=256m -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -XX:+UseLargePages -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=80 -XX:+UseCMSInitiatingOccupancyOnly -Dsun.rmi.dgc.server.gcInterval=0x7FFFFFFFFFFFFFFE -Dsun.rmi.dgc.client.gcInterval=0x7FFFFFFFFFFFFFFE -Djava.net.preferIPv4Stack=true -classpath :/usr/ssn/jms/CURRENT/ssn_home/ssnjms/jms/bin/run.jar:/lib/tools.jar org.jboss.Main -c messaging -Dssn.jndi.port=10000 -Dssn.jndi.rmi.port=10001 -Dssn.webservice.port=10002 -Dssn.invoker.jrmp.rmi.port=10003 -Dssn.invoker.pooled.rmi.port=10004 -Dssn.ha.jndi.port=10017 -Dssn.ha.jndi.rmi.port=10001 -Dssn.ha.invoker.jrmp.port=10006 -Dssn.ha.invoker.pooled.port=10007 -Djboss.partition.name=ssnjms -Djboss.hapartition.mcast_port=10020 -Djboss.webpartition.mcast_port=10021 -Djboss.ejb3sfsbpartition.mcast_port=10022 -Djboss.ejb3entitypartition.mcast_port=10023 -Djboss.messaging.datachanneludpport=45567 -Dssn.http.port=10008 -Dssn.jnp.port=10009 -Djboss.partition.udpGroup=230.47.29.9 -Dssn.corba.service.port=10010 -Dssn.jmx.rmi.adaptor.port=10011 -Dssn.snmp.agent.logger.port=10012 -Dssn.snmp.agent.adaptor.port=10013 -Dssn.messaging.service.uil2.port=10014 -Dssn.ejb3.connector.port=10015 -Dssn.messaging.connector.secure.bisocket.port=10018 -Dssn.messaging.connector.bisocket.port=10016 -Dssn.bisocket.secondary.bind.port=11000 -Dssn.bisocket.secondary.connect.port=11000 -Dssn.default.remoting.transport.connector.port=10024 -Dssn.jboss.bind.port=10025 -Dssn.db.user=ssnjms -Dssn.db.password=nj/a2fIuFOvUWesl5B8elA== -Dssn.db.host=jms01.gold01.uiq.bgesg.net -Dssn.db.port=3306 -Dssn.db.name=jmsdb -Dssn.db.type=mySQL -Dssn.db.driver.name=com.mysql.jdbc.Driver -Dssn.cluster.nodeid=1 -Dssn.uiq.jms.username=uiq -Dssn.uiq.jms.password=UH+pA2H/HDA4JbJXYMWwjw== -Dssn.uiq.jms.username=uiq -Dssn.uiq.jms.password=UH+pA2H/HDA4JbJXYMWwjw== -Dssnexportq.maxsize=1000000 -Dssnexportq.fullsize=1000000 -Dodseventq.maxsize=1000000 -Dodseventq.fullsize=1000000 -Dfieldstatq.maxsize=1000000 -Dfieldstatq.fullsize=1000000 -Dssneventq.maxsize=1000000 -Dssneventq.fullsize=1000000 -Dssnodrq.maxsize=1000000 -Dssnodrq.fullsize=1000000 -Dssnfwueventq.maxsize=1000000 -Dssnfwueventq.fullsize=1000000 -Dssnmpceventq.maxsize=1000000 -Dssnmpceventq.fullsize=1000000 -Dssndefaultq.maxsize=1000000 -Dssndefaultq.fullsize=1000000 -Dheartbeatq.maxsize=1000000 -Dheartbeatq.fullsize=1000000 -Dnem.snmp.traps.maxsize=1000000 -Dnem.snmp.traps.fullsize=1000000 -Dgmr.snmp.traps.maxsize=1000000 -Dgmr.snmp.traps.fullsize=1000000 -Dods.snmp.traps.maxsize=1000000 -Dods.snmp.traps.fullsize=1000000 -Dnmr.han.traps.maxsize=1000000 -Dnmr.han.traps.fullsize=1000000 -Dnmr.evse.traps.maxsize=1000000 -Dnmr.evse.traps.fullsize=1000000 -Dods.snmp.traps.fullsize=1000000 -Dnmr.ap.phonehome.maxsize=1000000 -Dnmr.ap.phonehome.fullsize=1000000 -Dnmr.ip.lease.alarm.maxsize=1000000 -Dnmr.ip.lease.alarm.fullsize=1000000 -Dnmr.ip.lease.count.maxsize=1000000 -Dnmr.ip.lease.count.fullsize=1000000 -Dnmr.threshold.maxsize=1000000 -Dnmr.threshold.fullsize=1000000 -Dods.last.comm.maxsize=1000000 -Dods.last.comm.fullsize=1000000 -Dregistrar.update.maxsize=1000000 -Dregistrar.update.fullsize=1000000 -Dnmr.voltmon.threshold.maxsize=10000 -Dnmr.voltmon.threshold.fullsize=10000 \ -Dvoltmon.external.threshold.maxsize=10000 -Dvoltmon.external.threshold.fullsize=10000 \ -DJBOSS_HOME=/usr/ssn/jms/CURRENT/ssn_home/ssnjms/jms -c messaging -b jms01.host

 

 

Thanks in advance if anyone can help!

Senior Member
tavor_a
Posts: 5
Registered: ‎07-26-2011
Message 2 of 4 (2,071 Views)

Re: Sitescope JMX monitor error 31008

Hi
can you tell what application you trying to monitor ,is it weblogic ?
Occasional Advisor
kucerjan
Posts: 10
Registered: ‎09-10-2012
Message 3 of 4 (2,042 Views)

Re: Sitescope JMX monitor error 31008

Step 1. Add below JAVA Option in to Jboss start up or configure file.

set "JAVA_OPTS=%JAVA_OPTS% -Djava.rmi.server.hostname="
set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port="
set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.authenticate=false"
set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.ssl=false"

Step 2. Restart Jboss Service

 or

 

Add the following code block to the applicable run.conf and restart the applicable JBoss instance.
### JConsole
# Default Settings
JAVA_OPTS="$JAVA_OPTS \-Dcom.sun.management.jmxremote \-Dcom.sun.management.jmxremote.port=9007 \-Dcom.sun.management.jmxremote.authenticate=false \-Dcom.sun.management.jmxremote.ssl=false"

 These are the two solutions I found on the internet, the first one is from the HP forums

 

Frequent Advisor
Richard Snader
Posts: 56
Registered: ‎09-08-2003
Message 4 of 4 (1,983 Views)

Re: Sitescope JMX monitor error 31008

Thank you so much!  My apologies for being so slow getting back to you!  This was a major help!  I really appreciate you taking your time to respond!  As it turns out, the vendor is not putting any counters out there, so we can only get basic JBoss stuff from it, and the counters I was hoping to find I had to get anotehr way!  Thanks again!

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.