Hello everybody,
I am using hyperic-HQ version 4.6.6.
I just started trying to get hyperic working at my place of business and am having issues with JMX/MBean autodiscovery. Our environement has java processes that run and have @ManagedResource / @ManagedOperation annotated spring beans for some of our methods and the like. After starting up my hq-agent on the deployed VM that is running these processes I See:
serverName - Solaris 10 | modified | server set changed | ||
serverName | NTP 4.x | /usr/lib/inet/xntpd | new | N/A |
serverName | Sendmail 8.x | /usr/sbin/sendmail | new | N/A |
serverName | HQ Agent 4.6.6 | /export/home/deploy/hyperic-hq-agent-4.6.6 | new | N/A |
in the autodiscovery section (where sever name is our actual server name). When I add this to my inventory, I see the following resources:
CPU, File Server, Network Server, NFS Mount, sshd process.
Nothing having to do with java, java processes, JMX or MBeans.
I have been working off of this documentation:
http://support.hyperic.com/display/DOCS46/Java+Applications
According to that documentation:
If your applications expose MBeans using the Spring 3.0 JMX annotations (@ManagedResource, @ManagedMetric, @ManagedAttribute, @ManagedOperation), they should automatically be exported with the required descriptors.
What am I doing wrong for these to not show up? Is there a flag I need to set in one of the properties files to turn on java/mbean autodiscovery, or is there something else I need to be doing? JMX is configureed for the running processes by Spring (not directly with -Dsun.remote..... command line args).
There are no errors in my agent.log, and it shows this block for discovery:
Any help would be greatly appreciated, this is really the main use case we are trying to get this up and running for.
Also, just re-checked agent.log and found this guy:
org.hyperic.hq.agent.AgentRemoteException: Failed to unschedule metrics for entity 2:10002: No measurement schedule for: 2:10002
at org.hyperic.hq.measurement.agent.server.MeasurementCommandsService.unscheduleMeasurements(MeasurementCommandsService.java:433)
at org.hyperic.hq.measurement.agent.server.MeasurementCommandsServer.dispatchCommand(MeasurementCommandsServer.java:167)
at org.hyperic.hq.agent.server.CommandDispatcher.processRequest(CommandDispatcher.java:113)
at org.hyperic.hq.agent.server.CommandListener.handleConn(CommandListener.java:216)
at org.hyperic.hq.agent.server.CommandListener.access$100(CommandListener.java:57)
at org.hyperic.hq.agent.server.CommandListener$AgentDispatchTask.run(CommandListener.java:200)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Message was edited by: developer1 Fixed capatalization error