-
Bug
-
Resolution: Done
-
Critical
-
JBoss A-MQ 6.3
-
None
-
None
When a network connector is stopped due to a BrokerStoppedException, the socket may remain open, causing the other broker to retain the clientId of the broker. Upon broker service restart, the broker cannot reestablish connection to the broker, because a connection with the same client id is already seen from the downstream broker.
- is related to
-
ENTMQ-2067 Broker Does Not Recover Cleanly from JDBC Datasource Outage
- Closed
-
ENTMQ-2422 broker logs 'remoteBrokerInfo is null' and does not re-establish network bridge
- Closed