DiscoveryTransport fails to find or connect to a Broker.
--------------------------------------------------------
Key: AMQNET-163
URL: https://issues.apache.org/activemq/browse/AMQNET-163
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ Client
Affects Versions: 1.0, 1.1
Reporter: Timothy Bish
Assignee: Timothy Bish
Fix For: 1.1
The DiscoveryTransport is not finding a remote Broker and once modified to
actually find one will crash due to some bad string handling code. The agent
is listening for the multicast events on the localhost adapter which isn't
correct, the broker defaults to sending the broadcast messages to
multicast://239.255.2.3:6155. Correcting that allows for the client to see the
broker.
Ideally the code should be much more configurable than it is to allow for the
client to observe broadcast messages on other addresses, however this would
require a lot of changes and would take to long to make it into the 1.1
release. A new issue will need to be created to address enhancements to the
DiscoveryTransport in a later release such as 1.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
