Gowrish SS
2013-05-07 01:43:14 UTC
Gowrish SS [http://community.zenoss.org/people/gowrish.ec] created the discussion
"Zenjmx - JBOSS error"
To view the discussion, visit: http://community.zenoss.org/message/73094#73094
--------------------------------------------------------------
Hi All,
I have some issues connecting to JMX Jboss application from zenoss, using zenoss 4.1.1, when i run zenjmx run -v10 -d <devicename>, i get the below error.
I can telnet to jboss server on the port specificed also i checked all zproperties corresponding to this device set correctly. could you please help.
2013-05-07 10:59:46,296 DEBUG zen.collector.scheduler: Task <device_name> starting on 300 second intervals
2013-05-07 10:59:46,296 DEBUG zen.collector.scheduler: Task <device_name> changing state from IDLE to QUEUED
2013-05-07 10:59:46,297 DEBUG zen.collector.scheduler: Task <device_name> changing state from QUEUED to RUNNING
2013-05-07 10:59:46,297 DEBUG zen.zenjmx: Scanning device <device_name> [<IP>]
2013-05-07 10:59:46,299 INFO zen.zenjmx: collectJMX(): for <device_name> RMI:jmxrmi:18080:944692ee66089e0a41230f43a0d352ce
[2013-05-07 10:59:46,375] [DEBUG] [qtp433064372-10] org.apache.xmlrpc.server.XmlRpcStreamServer:174 - execute: ->
[2013-05-07 10:59:46,527] [DEBUG] [qtp433064372-10] com.zenoss.zenpacks.zenjmx.ZenJmxService:46 - processing 51 datasources
[2013-05-07 10:59:46,532] [DEBUG] [qtp433064372-10] com.zenoss.zenpacks.zenjmx.call.Utility:96 - JMX URL is: service:jmx:rmi:///jndi/rmi://<IP>:18080/jmxrmi
2013-05-07 10:59:46,996 DEBUG zen.zenjmx: Sending 2 events, 0 perf events, 0 heartbeats
2013-05-07 10:59:48,656 DEBUG zen.collector.scheduler: tasks to clean set([<ZenPacks.zenoss.EnterpriseCollector.config.EnterpriseConfigurationLoaderTask object at 0x128a5a10>])
2013-05-07 10:59:48,656 DEBUG zen.collector.scheduler: Cleanup on task configLoader <ZenPacks.zenoss.EnterpriseCollector.config.EnterpriseConfigurationLoaderTask object at 0x128a5a10>
2013-05-07 10:59:48,656 DEBUG zen.collector.scheduler: Scheduler._cleanupTaskComplete: result=None task.name=configLoader
2013-05-07 11:00:11,986 DEBUG zen.pbclientfactory: pinging perspective
2013-05-07 11:00:11,987 DEBUG zen.pbclientfactory: perspective ponged
2013-05-07 11:00:11,988 DEBUG zen.pbclientfactory: Cancelling ping timeout
[2013-05-07 11:00:29,827] [DEBUG] [qtp433064372-10] com.zenoss.zenpacks.zenjmx.call.Utility:177 - Failed to connect to service:jmx:rmi:///jndi/rmi://<IP>:18080/jmxrmi [Nested Exception: java.rmi.ConnectException: Connection refused to host: <IP>; nested exception is:
       java.net.ConnectException: Connection timed out]
com.zenoss.jmx.JmxException: Failed to connect to service:jmx:rmi:///jndi/rmi://<IP>:18080/jmxrmi [Nested Exception: java.rmi.ConnectException: Connection refused to host: <IP>; nested exception is:
       java.net.ConnectException: Connection timed out]
       at com.zenoss.jmx.JmxClient.connect(JmxClient.java:142)
       at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.collect(ZenJmxService.java:101)
       at com.zenoss.zenpacks.zenjmx.ZenJmxService.collect(ZenJmxService.java:51)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
       at java.lang.reflect.Method.invoke(Unknown Source)
       at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.invoke(ReflectiveXmlRpcHandler.java:111)
       at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.execute(ReflectiveXmlRpcHandler.java:102)
       at org.apache.xmlrpc.server.XmlRpcServerWorker.execute(XmlRpcServerWorker.java:43)
       at org.apache.xmlrpc.server.XmlRpcServer.execute(XmlRpcServer.java:83)
       at org.apache.xmlrpc.server.XmlRpcStreamServer.execute(XmlRpcStreamServer.java:182)
       at org.apache.xmlrpc.webserver.XmlRpcServletServer.execute(XmlRpcServletServer.java:103)
       at org.apache.xmlrpc.webserver.XmlRpcServlet.doPost(XmlRpcServlet.java:120)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
       at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:534)
       at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:475)
       at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:405)
       at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
       at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:114)
       at org.eclipse.jetty.server.Server.handle(Server.java:352)
       at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:596)
       at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1069)
       at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:805)
       at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218)
       at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426)
       at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:241)
       at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:450)
       at java.lang.Thread.run(Unknown Source)
Caused by: java.rmi.ConnectException: Connection refused to host: <IP>; nested exception is:
       java.net.ConnectException: Connection timed out
       at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
       at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
       at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
       at sun.rmi.server.UnicastRef.invoke(Unknown Source)
       at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
       at javax.management.remote.rmi.RMIConnector.getConnection(Unknown Source)
       at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
       at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
       at com.zenoss.jmx.JmxClient.connect(JmxClient.java:137)
       ... 29 more
Caused by: java.net.ConnectException: Connection timed out
       at java.net.PlainSocketImpl.socketConnect(Native Method)
       at java.net.PlainSocketImpl.doConnect(Unknown Source)
       at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
       at java.net.PlainSocketImpl.connect(Unknown Source)
       at java.net.SocksSocketImpl.connect(Unknown Source)
       at java.net.Socket.connect(Unknown Source)
       at java.net.Socket.connect(Unknown Source)
       at java.net.Socket.<init>(Unknown Source)
       at java.net.Socket.<init>(Unknown Source)
       at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source)
       at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)
       ... 38 more
Regards

--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73094#73094]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Zenjmx - JBOSS error"
To view the discussion, visit: http://community.zenoss.org/message/73094#73094
--------------------------------------------------------------
Hi All,
I have some issues connecting to JMX Jboss application from zenoss, using zenoss 4.1.1, when i run zenjmx run -v10 -d <devicename>, i get the below error.
I can telnet to jboss server on the port specificed also i checked all zproperties corresponding to this device set correctly. could you please help.
2013-05-07 10:59:46,296 DEBUG zen.collector.scheduler: Task <device_name> starting on 300 second intervals
2013-05-07 10:59:46,296 DEBUG zen.collector.scheduler: Task <device_name> changing state from IDLE to QUEUED
2013-05-07 10:59:46,297 DEBUG zen.collector.scheduler: Task <device_name> changing state from QUEUED to RUNNING
2013-05-07 10:59:46,297 DEBUG zen.zenjmx: Scanning device <device_name> [<IP>]
2013-05-07 10:59:46,299 INFO zen.zenjmx: collectJMX(): for <device_name> RMI:jmxrmi:18080:944692ee66089e0a41230f43a0d352ce
[2013-05-07 10:59:46,375] [DEBUG] [qtp433064372-10] org.apache.xmlrpc.server.XmlRpcStreamServer:174 - execute: ->
[2013-05-07 10:59:46,527] [DEBUG] [qtp433064372-10] com.zenoss.zenpacks.zenjmx.ZenJmxService:46 - processing 51 datasources
[2013-05-07 10:59:46,532] [DEBUG] [qtp433064372-10] com.zenoss.zenpacks.zenjmx.call.Utility:96 - JMX URL is: service:jmx:rmi:///jndi/rmi://<IP>:18080/jmxrmi
2013-05-07 10:59:46,996 DEBUG zen.zenjmx: Sending 2 events, 0 perf events, 0 heartbeats
2013-05-07 10:59:48,656 DEBUG zen.collector.scheduler: tasks to clean set([<ZenPacks.zenoss.EnterpriseCollector.config.EnterpriseConfigurationLoaderTask object at 0x128a5a10>])
2013-05-07 10:59:48,656 DEBUG zen.collector.scheduler: Cleanup on task configLoader <ZenPacks.zenoss.EnterpriseCollector.config.EnterpriseConfigurationLoaderTask object at 0x128a5a10>
2013-05-07 10:59:48,656 DEBUG zen.collector.scheduler: Scheduler._cleanupTaskComplete: result=None task.name=configLoader
2013-05-07 11:00:11,986 DEBUG zen.pbclientfactory: pinging perspective
2013-05-07 11:00:11,987 DEBUG zen.pbclientfactory: perspective ponged
2013-05-07 11:00:11,988 DEBUG zen.pbclientfactory: Cancelling ping timeout
[2013-05-07 11:00:29,827] [DEBUG] [qtp433064372-10] com.zenoss.zenpacks.zenjmx.call.Utility:177 - Failed to connect to service:jmx:rmi:///jndi/rmi://<IP>:18080/jmxrmi [Nested Exception: java.rmi.ConnectException: Connection refused to host: <IP>; nested exception is:
       java.net.ConnectException: Connection timed out]
com.zenoss.jmx.JmxException: Failed to connect to service:jmx:rmi:///jndi/rmi://<IP>:18080/jmxrmi [Nested Exception: java.rmi.ConnectException: Connection refused to host: <IP>; nested exception is:
       java.net.ConnectException: Connection timed out]
       at com.zenoss.jmx.JmxClient.connect(JmxClient.java:142)
       at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.collect(ZenJmxService.java:101)
       at com.zenoss.zenpacks.zenjmx.ZenJmxService.collect(ZenJmxService.java:51)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
       at java.lang.reflect.Method.invoke(Unknown Source)
       at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.invoke(ReflectiveXmlRpcHandler.java:111)
       at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.execute(ReflectiveXmlRpcHandler.java:102)
       at org.apache.xmlrpc.server.XmlRpcServerWorker.execute(XmlRpcServerWorker.java:43)
       at org.apache.xmlrpc.server.XmlRpcServer.execute(XmlRpcServer.java:83)
       at org.apache.xmlrpc.server.XmlRpcStreamServer.execute(XmlRpcStreamServer.java:182)
       at org.apache.xmlrpc.webserver.XmlRpcServletServer.execute(XmlRpcServletServer.java:103)
       at org.apache.xmlrpc.webserver.XmlRpcServlet.doPost(XmlRpcServlet.java:120)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
       at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:534)
       at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:475)
       at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:405)
       at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
       at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:114)
       at org.eclipse.jetty.server.Server.handle(Server.java:352)
       at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:596)
       at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1069)
       at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:805)
       at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218)
       at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426)
       at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:241)
       at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:450)
       at java.lang.Thread.run(Unknown Source)
Caused by: java.rmi.ConnectException: Connection refused to host: <IP>; nested exception is:
       java.net.ConnectException: Connection timed out
       at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
       at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
       at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
       at sun.rmi.server.UnicastRef.invoke(Unknown Source)
       at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
       at javax.management.remote.rmi.RMIConnector.getConnection(Unknown Source)
       at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
       at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
       at com.zenoss.jmx.JmxClient.connect(JmxClient.java:137)
       ... 29 more
Caused by: java.net.ConnectException: Connection timed out
       at java.net.PlainSocketImpl.socketConnect(Native Method)
       at java.net.PlainSocketImpl.doConnect(Unknown Source)
       at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
       at java.net.PlainSocketImpl.connect(Unknown Source)
       at java.net.SocksSocketImpl.connect(Unknown Source)
       at java.net.Socket.connect(Unknown Source)
       at java.net.Socket.connect(Unknown Source)
       at java.net.Socket.<init>(Unknown Source)
       at java.net.Socket.<init>(Unknown Source)
       at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source)
       at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)
       ... 38 more
Regards

--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73094#73094]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]