1. Lingo
  2. LINGO-31

JmsJmxConnector & JmsJmxConnectorServer can't read destinationGroupName and destinationServerName from the environment


    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.2, 1.2.1
    • Fix Version/s: 1.4
    • Labels:
    • Number of attachments :


      In an environment where multiple servers publish MBeans with the same name over a single jms broker, there really isn't any way (or at least I couldn't find one) to distinguish these beans from each other, even though the documentation in says this should be possible via the environment variables.

      Looking at the code, I can't find a way how this could work as described by the documentation:

      • The environment map doesn't seem to get touched by the connectors. How could any variable be populated based on this map?
      • The code does seem to (try to) populate some properties from the URL. This has a few problems though. At least ActiveMQ seems to dislike any additional parameters in the URL, causing exceptions to be thrown. The second, even worse problem is that the ActiveMQ IntrospectionSupport, that is used for setting the properties, seems to be looking for setters of the properties, which there aren't any, so even if the values were given as URL parameters, they will not end up set in the connector.


        There are no comments yet on this issue.


          • Assignee:
            Mikko Wilkman


            • Created: