JBoss Messaging custom queue's not being discovered

[mzeijen]

I would like to monitor my JBoss Messaging message queue's. These queue's have custome JMX domain names. For example: com.docmorris.log.destination:name=log.esb.dlq,service=Queue

Somehow Jopr doesn't discover these queue's. I also can't seem to find how I can add these manually. What should I do?

[mazz]

(Heiko replied to the mailing list by accident - I'm posting his reply here)

Indeed - They are discovered if they follow this naming scheme:

jboss.messaging.destination:service=Queue,name=%name%|jboss.esb.*:service=Queue,name=%name%

(same for topic)

You can edit the plugin-descriptor for the JbossAS plugin and add your pattern there - something like

jboss.messaging.destination:service=Queue,name=%name%|jboss.esb.*:service=Queue,name=%name%|com.docmorris.*:service=Queue,name=%name%

We can't just discoveri .*:service=Queue,name=%name% --as this will clash with e.g. resources from JBossMQ

[mazz]

Although, I think you do not have to do what Heiko mentions to get this to work.

The JMS beans are backed by MBeans - and that MBean name is configurable in the Inventory tab. I'm looking at JMS resources under the RHQ Server resource, and in the Inventory tab's connection properties, I see the MBean name that is configurable here.

I suspect if you manually create your JMS resources, and set your MBean in there, it would work. This is all doable via the UI - you won't have to mess with the plugin jars.

I haven't tried to manually create JMS beans or configured them with custom object names, let us know how it works out. I suspect this will work though.

[mazz]

Grrrr... it seems the object name here is read-only - you can edit the other fields, just not the important one you need to change.

Anyone know why this field is read-only? Is this what makes up the resource key perhaps?

[mzeijen]

Thanks for the help. I'll change the plugin descriptor.

Would be great though if something like that became configurable via the user interface.

[mzeijen]

I finally got the time to try this. The problem I have is that I don't now how I can deploy the changed jopr-jboss-as-plugin jar. I copied it to the ${deploy}/rhq.ear/rhq-downloads/rhq-plugins directory but the agents don't seem to pick it up. I did force a plugin update in the agent console.

I am currently working with JOPR 2.2.0.Beta1

[pilhuhn]

You need to run 'plugins update' in the agent -- or the respective operation from the UI

[mzeijen]

I did try that. But it tells me that all plugins are up to date.