Quantcast
Channel: VMware Communities : Popular Discussions - Hyperic User Forums
Viewing all articles
Browse latest Browse all 52618

Probably simple, How do I autodiscover MBeans?

$
0
0

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:

 

 


s
erverName - Solaris 10
modifiedserver set changed
   serverNameNTP 4.x/usr/lib/inet/xntpdnewN/A
   serverNameSendmail 8.x/usr/sbin/sendmailnewN/A
   serverNameHQ Agent 4.6.6/export/home/deploy/hyperic-hq-agent-4.6.6newN/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:

Applications using Spring 3.0 JMX Annotations

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:

 

28-06-2012 16:15:21,569 CDT INFO  [Thread-4] [RuntimeAutodiscoverer@266] Running runtime autodiscovery for ProcessServer
28-06-2012 16:15:21,588 CDT INFO  [Thread-4] [RuntimeAutodiscoverer@275] ProcessServer discovery took 0.01
28-06-2012 16:15:21,588 CDT INFO  [Thread-4] [RuntimeAutodiscoverer@266] Running runtime autodiscovery for NetworkServer
28-06-2012 16:15:21,594 CDT INFO  [Thread-4] [RuntimeAutodiscoverer@275] NetworkServer discovery took 0
28-06-2012 16:15:21,595 CDT INFO  [Thread-4] [RuntimeAutodiscoverer@266] Running runtime autodiscovery for Net Services
28-06-2012 16:15:21,603 CDT INFO  [Thread-4] [RuntimeAutodiscoverer@275] Net Services discovery took 0
28-06-2012 16:15:21,603 CDT INFO  [Thread-4] [RuntimeAutodiscoverer@266] Running runtime autodiscovery for FileServer
28-06-2012 16:15:21,609 CDT INFO  [Thread-4] [RuntimeAutodiscoverer@275] FileServer discovery took 0

 

 

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)

not sure if that matters, but I don't expect it should.  Everything is normal in the logs after that entry.

 

 

Message was edited by: developer1  Fixed capatalization error


Viewing all articles
Browse latest Browse all 52618

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>