An endpoint that is used by multiple receivers breaks MBean registration (JMX Agent)

Details

  • Similar Issues:
    None

Description

I created an endpoint using a JMS Topic endpoint in order to implement a publish-subscribe infrastructure. In this setting there are multiple receivers listening on the same endpoint. The way the JmxAgent is implemented, it iterates through endpoints, from a receiver's perspective, and creates MBeans. Since my JMS Topic endpoint is used/referenced by two receivers, it is added to the MBean list twice. During initialization of the JMX Agent, it iterates through this list of MBeans and starts regestering them one-by-one with the MBean server. The first one in the list registeres without any problems, but the second generates an exception (javax.management.InstanceAlreadyExistsException).

It should be relatively easy to fix, but will require to decide wether an endpoint can appear twice as an MBean, once for each receiver, or not...

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ross Mason added a comment -

Hi Rune,

You can name your endpoints explicitly to avoid duplicate names using -

<endpoint address="jms://topic:my.topic" name="myTopicEndpoint1"/>

If you name each differently there shouldn't be a problem

Cheers,

Ross

Show
Ross Mason added a comment - Hi Rune, You can name your endpoints explicitly to avoid duplicate names using - <endpoint address="jms://topic:my.topic" name="myTopicEndpoint1"/> If you name each differently there shouldn't be a problem Cheers, Ross
Hide
Permalink
Andrew Perepelytsya added a comment -

All old Resolved issues transitioned into a Closed state.

Show
Andrew Perepelytsya added a comment - All old Resolved issues transitioned into a Closed state.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: