Archived community.zenoss.org | full text search
Skip navigation
Up to Discussions in zenoss-zenpacks
12934 Views 11 Replies Latest reply: Aug 13, 2010 11:31 PM by nick.anderson RSS
nick.anderson Rank: White Belt
nick.anderson
18 posts since
Mar 2, 2010
Currently Being Moderated

Aug 5, 2010 3:42 PM

zenjmx zenpack connection issues

It's very possible I am just being daft and missing something obvious but for the life of me I cannot seem to get the jmx zenpack to work.

 

 

Running ZenJMX 3.5.2, Zenoss 3.0, centos 5 64bit

 

The zenpack installed without issue. I installed the latest sun jre:

 

[zenoss]$ java -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)

 

the zenjmx service is running

 

I have the jmx port on a java instance listening on 9898 without ssl and without auth. Connecting to that with jconsole works without issue.

 

I am a bit confused by the two templates provided by the ZenJMX zenpack one called Java and one called ZenJMX. I have tried binding both to my device and set the zJmxManagementPort to 9898. I have also tried setting the Management port inside the templates datasouces both with no success. I continue to get "error connecting to server" events for each datasource.

 

Any help is greatly appriciated.

Tags: zenjmx, 3.0
  • jplouis ZenossEmployee
    jplouis
    93 posts since
    May 7, 2008
    Currently Being Moderated
    1. Aug 5, 2010 3:55 PM (in response to nick.anderson)
    Re: zenjmx zenpack connection issues

    the ZenJMX template is meant to monitor the zenjmx process itself; you can ignore it

     

    Use the Java template.  While there is a zProperty for the jmx port to use, your datasources in the template are probably not referencing the zproperty

  • nick.anderson Rank: White Belt
    nick.anderson
    18 posts since
    Mar 2, 2010
    Currently Being Moderated
    2. Aug 5, 2010 4:25 PM (in response to jplouis)
    Re: zenjmx zenpack connection issues

    Ok thanks for that clarification. I unbound the zenjmx template from my device and now am left only with the Java template.


    I created a local copy/overrode the template onto the device whatever you want to call it in 3.0. And I edited each of the data sources Management Port field to be 9898 (the port that works with jconsole). Is there another field that I should be editing that I am not? I still am getting connection error events for each of the Java template data sources on my device.

  • nick.anderson Rank: White Belt
    nick.anderson
    18 posts since
    Mar 2, 2010
    Currently Being Moderated
    3. Aug 5, 2010 6:02 PM (in response to nick.anderson)
    Re: zenjmx zenpack connection issues

    [2010-08-05 17:00:12,608] [DEBUG] [btpool0-1] com.zenoss.zenpacks.zenjmx.ZenJmxService:46 - processing 4 datasources
    [2010-08-05 17:00:12,614] [DEBUG] [btpool0-1]com.zenoss.zenpacks.zenjmx.call.Utility:173 - Datasource Thread Count manageIp or device properties not specified

        at com.zenoss.zenpacks.zenjmx.call.Utility.getUrl(Utility.java:81)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.createJmxClient(ZenJmxService.java:189)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.collect(ZenJmxService.java:100)

        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.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)

        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)

        at org.mortbay.jetty.Server.handle(Server.java:303)

        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)

        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:735)

        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:636)

        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)

        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)

        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217)

        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

     

    [2010-08-05 17:00:12,632] [DEBUG] [btpool0-1] com.zenoss.zenpacks.zenjmx.call.Utility:173 - Datasource Thread Count manageIp or device properties not specified

    com.zenoss.zenpacks.zenjmx.call.ConfigurationException: Datasource Thread Count manageIp or device properties not specified

        at com.zenoss.zenpacks.zenjmx.call.Utility.getUrl(Utility.java:81)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.createJmxClient(ZenJmxService.java:189)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.collect(ZenJmxService.java:100)

        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.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)

        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)

        at org.mortbay.jetty.Server.handle(Server.java:303)

        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)

        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:735)

        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:636)

        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)

        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)

        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217)

        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

     

    [2010-08-05 17:00:12,633] [DEBUG] [btpool0-1] com.zenoss.zenpacks.zenjmx.call.Utility:173 - Datasource Thread Count manageIp or device properties not specified

    com.zenoss.zenpacks.zenjmx.call.ConfigurationException: Datasource Thread Count manageIp or device properties not specified

        at com.zenoss.zenpacks.zenjmx.call.Utility.getUrl(Utility.java:81)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.createJmxClient(ZenJmxService.java:189)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.collect(ZenJmxService.java:100)

        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.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)

        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)

        at org.mortbay.jetty.Server.handle(Server.java:303)

        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)

        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:735)

        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:636)

        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)

        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)

        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217)

        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

     

    [2010-08-05 17:00:12,644] [DEBUG] [btpool0-1] com.zenoss.zenpacks.zenjmx.call.Utility:173 - Datasource Thread Count manageIp or device properties not specified

    com.zenoss.zenpacks.zenjmx.call.ConfigurationException: Datasource Thread Count manageIp or device properties not specified

        at com.zenoss.zenpacks.zenjmx.call.Utility.getUrl(Utility.java:81)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.createJmxClient(ZenJmxService.java:189)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.collect(ZenJmxService.java:100)

        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.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)

        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)

        at org.mortbay.jetty.Server.handle(Server.java:303)

        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)

        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:735)

        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:636)

        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)

        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)

        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217)

        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

     

    [2010-08-05 17:00:12,646] [INFO ] [btpool0-1] com.zenoss.zenpacks.zenjmx.ZenJmxService:53 - finished processing 4 datasources for device psomonitor.ut06nxg03-ypc.pso.netopia.com in 38 ms

    [2010-08-05 17:00:12,647] [DEBUG] [btpool0-1] org.apache.xmlrpc.server.XmlRpcStreamServer:186 - execute: Request performed successfully

    [2010-08-05 17:00:12,680] [DEBUG] [btpool0-1] org.apache.xmlrpc.server.XmlRpcStreamServer:234 - execute: <-

    [2010-08-05 17:00:17,513] [DEBUG] [btpool0-1] org.apache.xmlrpc.server.XmlRpcStreamServer:174 - execute: ->

    [2010-08-05 17:00:17,589] [DEBUG] [btpool0-1] com.zenoss.zenpacks.zenjmx.ZenJmxService:46 - processing 4 datasources

    [2010-08-05 17:00:17,591] [DEBUG] [btpool0-1] com.zenoss.zenpacks.zenjmx.call.Utility:173 - Datasource Thread Count manageIp or device properties not specified

    com.zenoss.zenpacks.zenjmx.call.ConfigurationException: Datasource Thread Count manageIp or device properties not specified

        at com.zenoss.zenpacks.zenjmx.call.Utility.getUrl(Utility.java:81)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.createJmxClient(ZenJmxService.java:189)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.collect(ZenJmxService.java:100)

        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.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)

        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)

        at org.mortbay.jetty.Server.handle(Server.java:303)

        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)

        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:735)

        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:636)

        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)

        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)

        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217)

        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

     

    [2010-08-05 17:00:17,592] [DEBUG] [btpool0-1] com.zenoss.zenpacks.zenjmx.call.Utility:173 - Datasource Thread Count manageIp or device properties not specified

    com.zenoss.zenpacks.zenjmx.call.ConfigurationException: Datasource Thread Count manageIp or device properties not specified

        at com.zenoss.zenpacks.zenjmx.call.Utility.getUrl(Utility.java:81)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.createJmxClient(ZenJmxService.java:189)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.collect(ZenJmxService.java:100)

        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.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)

        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)

        at org.mortbay.jetty.Server.handle(Server.java:303)

        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)

        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:735)

        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:636)

        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)

        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)

        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217)

        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

     

    [2010-08-05 17:00:17,593] [DEBUG] [btpool0-1] com.zenoss.zenpacks.zenjmx.call.Utility:173 - Datasource Thread Count manageIp or device properties not specified

    com.zenoss.zenpacks.zenjmx.call.ConfigurationException: Datasource Thread Count manageIp or device properties not specified

        at com.zenoss.zenpacks.zenjmx.call.Utility.getUrl(Utility.java:81)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.createJmxClient(ZenJmxService.java:189)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.collect(ZenJmxService.java:100)

        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.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)

        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)

        at org.mortbay.jetty.Server.handle(Server.java:303)

        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)

        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:735)

        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:636)

        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)

        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)

        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217)

        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

     

    [2010-08-05 17:00:17,595] [DEBUG] [btpool0-1] com.zenoss.zenpacks.zenjmx.call.Utility:173 - Datasource Thread Count manageIp or device properties not specified

    com.zenoss.zenpacks.zenjmx.call.ConfigurationException: Datasource Thread Count manageIp or device properties not specified

        at com.zenoss.zenpacks.zenjmx.call.Utility.getUrl(Utility.java:81)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.createJmxClient(ZenJmxService.java:189)

        at com.zenoss.zenpacks.zenjmx.ZenJmxService$JMXCollector.collect(ZenJmxService.java:100)

        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.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)

        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)

        at org.mortbay.jetty.Server.handle(Server.java:303)

        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)

        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:735)

        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:636)

        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)

        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)

        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217)

        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

  • jplouis ZenossEmployee
    jplouis
    93 posts since
    May 7, 2008
    Currently Being Moderated
    4. Aug 6, 2010 12:05 PM (in response to nick.anderson)
    Re: zenjmx zenpack connection issues

    Your device doesn't have a manageIP attribute which means zenjmx can't figure out the host.

  • nick.anderson Rank: White Belt
    nick.anderson
    18 posts since
    Mar 2, 2010
    Currently Being Moderated
    5. Aug 6, 2010 12:33 PM (in response to jplouis)
    Re: zenjmx zenpack connection issues

    How do I set the manageIP attribute then? Isn't that something that is

    automatically determined from a lookup of the device name.

  • jplouis ZenossEmployee
    jplouis
    93 posts since
    May 7, 2008
    Currently Being Moderated
    6. Aug 6, 2010 3:47 PM (in response to nick.anderson)
    Re: zenjmx zenpack connection issues

    when you add the device it sets the IP if you let modeling occur.  SInce you already have the device you can just model it.  In 3.0 the the model device option is on the device's page in the gear menu on the bottom left

  • nick.anderson Rank: White Belt
    nick.anderson
    18 posts since
    Mar 2, 2010
    Currently Being Moderated
    7. Aug 6, 2010 4:02 PM (in response to jplouis)
    Re: zenjmx zenpack connection issues

    Yes, I have modeled and re-modeled the device. Tried adding a device by

    ip instead of name. Tried resetting the IP on the device. Nothing gets

    rid of that error in the zenjmx logs.

     

    This zenpack was installed after 3.0 upgrade, but that shouldn't make

    any difference.

  • nick.anderson Rank: White Belt
    nick.anderson
    18 posts since
    Mar 2, 2010
    Currently Being Moderated
    8. Aug 9, 2010 11:35 AM (in response to nick.anderson)
    Re: zenjmx zenpack connection issues

    Re-installing the zenpack seems to make no difference. I can successfully collect jmx data with the nagios check_jmx  plugin and a custom command datasource.

     

    Preparing Command...
    Executing command /usr/local/zenoss/zenoss/libexec/check_jmx/nagios/plugin/check_jmx -U  service:jmx:rmi:///jndi/rmi://192.168.0.94:9898/jmxrmi -O  java.lang:type=Memory -A HeapMemoryUsage -K used -I HeapMemoryUsage -J  used -vv    against 192.168.0.94
    JMX OK
    HeapMemoryUsage.used=293936192
    293936192
    DONE in 0 seconds

    Any ideas how to fix the jmx data source?
  • jplouis ZenossEmployee
    jplouis
    93 posts since
    May 7, 2008
    Currently Being Moderated
    9. Aug 9, 2010 10:37 PM (in response to nick.anderson)
    Re: zenjmx zenpack connection issues

    can you go into zendmd and try the following, where 'device_id' is the name of your device

     

    d = dmd.Devices.findDevice('device_id')

    d.manageIp

     

    you should also be able to see the ip address in the UI on both the infrastructure device list page and the device's page.

     

    For whatever reason it doesn't seem like your device has a manage ip.  What is the last model time for the device? Time should be in the UI

  • nick.anderson Rank: White Belt
    nick.anderson
    18 posts since
    Mar 2, 2010
    Currently Being Moderated
    10. Aug 11, 2010 9:52 AM (in response to jplouis)
    Re: zenjmx zenpack connection issues

    Thanks for the tips. I think I have figured out what happend, though I'm not sure how to avoid it in the future.

     

    I have multiple JVM instances running on one server. Each JVM is bound to a different IP. The "system" IP is used to monitor the server via snmp etc ... Each jvm instance runs a page server so I am monitoring each of those as their own device with the HTTPMonitor. I wanted to monitor the JVM on that device as well.

     

    I think that my problem was stemming from the model on the "system IP" picking up all the IPs attached to the system.

     

    I deleted the "system" device and all the JMX monitors started working.

     

    It's not quite clear to me how to avoid this, adding the system in after the JMX monitors seems to work, but that prevents me from adding any additional jmx monitors on that host without deleting the system device first.

  • nick.anderson Rank: White Belt
    nick.anderson
    18 posts since
    Mar 2, 2010
    Currently Being Moderated
    11. Aug 13, 2010 11:31 PM (in response to nick.anderson)
    Re: zenjmx zenpack connection issues

    I'm still not sure of the best way to deal with the IP issue going forward. But it seems another issue has come to light. Apparently JMX binds to 0.0.0.0, this obviously causes issues when you are running multiple JVM instances each wanting to listen on the same port. The solution to correct that seems more complicated than setting the JMX port for each monitored device. So I went to edit the management port on the template to ${here/zJMXManagementPort} but the interface wont let me enter anything except a number. This seems to be a bug in the zenpack. I can of course override the template on each device, but that becomes painful when I add new beans to be monitored. Any ideas?

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points