#1 Unable to query java.lang and others

[Anonymous]

I've installed the bean in a JBoss-5.1 server. I can successfully query the following:
jboss.system:type=ServerInfo TotalMemory
jboss.system:type=ServerInfo ActiveThreadCount
jboss.web:type=ThreadPool,name=ajp-0.0.0.0-8009 currentThreadsBusy
jboss.web:type=ThreadPool,name=ajp-0.0.0.0-8009 currentThreadCount
jboss.web:type=GlobalRequestProcessor,name=ajp-0.0.0.0-8009 *requestCount
jboss.web:type=GlobalRequestProcessor,name=ajp-0.0.0.0-8009 maxTime
jboss.web:type=Manager,path=/,host=localhost activeSessions
jboss.web:type=Manager,path=/,host=localhost maxActive
jboss:service=TransactionManager *RollbackCount
jboss:service=TransactionManager *CommitCount

However, I'm unable to query any of the following, even though they are plainly available through JConsole
java.lang:type=Memory HeapMemoryUsage
java.lang:type=Memory NonHeapMemoryUsage
java.lang:type=Memory ObjectPendingFinalizationCount
java.lang:name=Copy,type=GarbageCollector *CollectionCount
java.lang:name=Copy,type=GarbageCollector *CollectionTime
java.lang:name=MarkSweepCompact,type=GarbageCollector *CollectionCount
java.lang:name=MarkSweepCompact,type=GarbageCollector *CollectionTime
java.lang:type=OperatingSystem SystemLoadAverage
java.lang:type=OperatingSystem OpenFileDescriptorCount
java.lang:type=OperatingSystem FreePhysicalMemorySize
jboss.mq.destination:service=Queue,name=DLQ QueueDepth
jboss.mq.destination:service=Queue,name=DLQ SubscribersCount
jboss.mq.destination:service=Queue,name=DLQ ReceiversCount
jboss.jca:service=ManagedConnectionPool,name=SORDataSource AvailableConnectionCount
Hibernate:name=statistics *SuccessfulTransactionCount
Hibernate:name=statistics *OptimisticFailureCount
Hibernate:name=statistics *TransactionCount
oracle.ucp.admin.UniversalConnectionPoolMBean:name=UniversalConnectionPoolManager availableConnectionsCount

FWIW, I'm running Sun/Oracle java version "1.6.0_24" on Solaris-x86_64

[Tobias Frech]

Hi there!
For being able to access java.lang MBeans the JBoss/JDK integration of the two MBeans servers should be activated. Unfortunately JBoss 5.1 seems to have a bug that does not allow to do that in this version. JConsole accesses the JDK MBeans by default, jmx-console the JBoss MBeans.
jboss.mq MBeans are used for JBoss MQ (the old messaging). JBoss 5.1 has switched to JBoss Messaging (new). The MBean names probably have changed.
The Hibernate statistics MBeans only can be seen if the statistics feature is enabled in Hibernate. Same for the Oracle JDBC driver.
I hope this clarified some things.
Cheers,
Tobias

[Tobias Frech]

See the new -javaagent option which was exactly created to solve the described problem with JBoss 5.1.