activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Closed) (JIRA)" <>
Subject [jira] [Closed] (AMQ-1657) Bad Things Happen when 2 brokers in Network of Brokers have same name
Date Fri, 30 Sep 2011 20:40:46 GMT


Timothy Bish closed AMQ-1657.

    Resolution: Won't Fix
> Bad Things Happen when 2 brokers in Network of Brokers have same name
> ---------------------------------------------------------------------
>                 Key: AMQ-1657
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 4.1.1
>            Reporter: Aaron Mulder
>             Fix For: NEEDS_REVIEWED
> If you configure a Network of Brokers with 2 brokers, and in the config file, both have
the same broker name (and same network connection names), then there seem to be some pretty
unpleasant effects.  At a minimum, lots of startup errors and dropped connections between
the two brokers due to errors in DemandForwardingBridge like FirstBroker is already subscribed
to temporary topic foo and so on.  I suspect it also causes messages sent to one broker to
not always be forwarded to the other broker, though that might be because the broker connection
is temporarily down due to the errors like mentioned above.  (However, the symptoms may be
hidden depending on your log levels!)
> It would be nice if during startup, if one broker in the network connects to another
and determines that they both have the same name, there would be some sort of catastrophic
error that caused the starting broker to immediately shut down with a useful error message.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message