Need the JNDI name for Destinations present in JMS Modules

Question

Hi all,
I need JNDI`s of all the Destinations present in JMS Modules. With this code i am able to get all info about the JMS Modules, Destinations and as well as information about messages, but still not able to extract JNDI of Destination. Can some one give me pointer on this ?
try {
JMXServiceURL serviceUrl =
new JMXServiceURL(
"service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.runtime");
System.out.println("Connecting to: " + serviceUrl);
Hashtable env = new Hashtable();
env.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES,
"weblogic.management.remote");
env.put(javax.naming.Context.SECURITY_PRINCIPAL, "weblogic");
env.put(javax.naming.Context.SECURITY_CREDENTIALS, "welcome1");
jmxCon = JMXConnectorFactory.newJMXConnector(serviceUrl, env);
jmxCon.connect();
MBeanServerConnection con = jmxCon.getMBeanServerConnection();
Set<ObjectName> mbeans = con.queryNames(queryObjectName, null);
for (ObjectName mbeanName : mbeans) {
String temp = mbeanName.toString();
System.out.println(temp);
String[] mBeanAttributes = {"Name", "DestinationType", "MessagesCurrentCount",
"MessagesPendingCount", "MessagesReceivedCount", "MessagesHighCount" };
queryObjectName = new ObjectName("*:*,Type=JMSDestinationRuntime");
mbeans = con.queryNames(queryObjectName, null);
for (ObjectName mbeanName : mbeans) {
AttributeList attributes = con.getAttributes(mbeanName, mBeanAttributes);
System.out.println((Attribute) attributes.get(0)+ "" +
(Attribute) attributes.get(1)+
(Attribute) attributes.get(2)+
(Attribute) attributes.get(3)+
(Attribute) attributes.get(4)+
(Attribute) attributes.get(5));
String temp = mbeanName.toString();
ObjectInstance inst = con.getObjectInstance(mbeanName);
System.out.println(temp);
finally {
if (jmxCon != null)
jmxCon.close();
But Nowhere i am getting the JNDI of destination Queues or Topics.
Edited by: mdev on Feb 21, 2012 5:21 PM

Answer 1

You are accessing the runtime mbean of a JMS destination. The JNID name of a destination is not available on the runtime destination MBean.
If you are using jms-system-resource to deploy your JMS module, you should be able to access the deployment mbean of the destination. The starting MBean for JMS is JMSSystemResourceMBean in this case.