ray.wood

JBOSS Monitoring?

Discussion created by ray.wood on Jul 27, 2011
Latest reply on Jul 27, 2011 by ray.wood

Has anyone succesfully demonstrated the JBOSS probe on our demo system?

 

We have an instance of the probe running on /Nimsoft-Demo/WorldWideHQ/clusternode1 and it is configured to connect to a resource on 192.168.128.92:1099. It appears to connect OK and discovers a load of JMX classes but there are very few metrics with any values.

 

The help for the Jboss probe recommends monitoring the following metrics:

 

Memory
jboss.system -> ServerInfo -> name
 FreeMemory
 TotalMemory
 MaxMemory

Threads
jboss.web -> ThreadPool -> http-0.0.0.0-8080
 currentThreadCount          
 currentThreadsBusy

Connections
jboss.jca -> ManagedConnectionPool -> JmsXA
 InUseConnectionCount
 ConnectionCount

jboss.jca -> ManagedConnectionPool -> DefaultDS
 InUseConnectionCount 
 ConnectionCount

Sent/received
jboss.web -> GlobalRequestProcessor -> http-0.0.0.0-8080
 bytesSent
 bytesReceived 
 requestCount
 errorCount

However, none of these metrics seem to exist within the jboss probe on our system.

I'm interested in knowing whether this used to work and has now broken for some reason or has it never worked.

 

Thanks

Ray

Outcomes