activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerald Loeffler (JIRA)" <j...@apache.org>
Subject [jira] Created: (AMQ-1489) discoveryUri in transportConnector and uri in networkConnector partially ignored if multicast
Date Wed, 07 Nov 2007 12:22:22 GMT
discoveryUri in transportConnector and uri in networkConnector partially ignored if multicast
---------------------------------------------------------------------------------------------

                 Key: AMQ-1489
                 URL: https://issues.apache.org/activemq/browse/AMQ-1489
             Project: ActiveMQ
          Issue Type: Bug
          Components: Connector
    Affects Versions: 4.1.1
            Reporter: Gerald Loeffler
             Fix For: 4.1.2


This bug relates to the MulticastDiscoveryAgent and was discovered when 

1. the discoveryUri of a transportConnector is a multicast-uri such as

{code:xml}
<transportConnector uri="..." discoveryUri="multicast://239.3.7.0:37000" />
{code}

or

2. the uri of a networkConnector is a multicast-uri such as

{code:xml}
<networkConnector name="..." uri="multicast://239.3.7.0:37000">
{code}

In these cases, the uri is partially ignored by the MulticastDiscoveryAgent: the host-name
of the uri (239.3.7.0) is extracted and used as the group name by the MulticastDiscoveryAgent.
But the actual multicast group IP is always 239.255.2.3 and the multicast port is always 6155,
regardless of what the actual uri is in the configuration.

The reason for this is that MulticastDiscoveryAgentFactory creates a new MulticastDiscoveryAgent
and sets the group based on the uri's host, but fails to set the discoveryURI itself. MulticastDiscoveryAgentFactory
should be corrected to do this:

{code:java}
MulticastDiscoveryAgent rc = new MulticastDiscoveryAgent();
rc.setDiscoveryURI(uri); // missing
rc.setGroup(uri.getHost());
{code}

Without the above setting of the discoveryURI the MulticastDiscoveryAgent always uses the
DEFAULT_DISCOVERY_URI_STRING which is "multicast://239.255.2.3:6155", explaining the erroneous
behaviour described above.

  kind regards,
  gerald

http://www.gerald-loeffler.net


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message