[
https://issues.apache.org/jira/browse/AMQ-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Koerner updated AMQ-4097:
-----------------------------
Summary: Broker-to-Broker Reconnect fails wrongly due to duplicate name
(was: Broker-to-Broker Reconnect fails due to duplicate name)
> Broker-to-Broker Reconnect fails wrongly due to duplicate name
> --------------------------------------------------------------
>
> Key: AMQ-4097
> URL: https://issues.apache.org/jira/browse/AMQ-4097
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.7.0
> Environment: A central broker to which a lot (50+) of external
> brokers connect with a duplex bridge. A special routing/firewall is used
> which can affect timing but not order of TCP packets. This can be simulated
> by using socat.
> Reporter: Ron Koerner
>
> The situation is as follows:
> - an external broker A connects
> - time passes
> - a lot of external brokers disconnect including A
> - A reconnects
> - wrong message about duplicate name is generated
> A logfile excerpt is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
