[
https://issues.apache.org/activemq/browse/AMQ-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-2927.
--------------------------------
Fix Version/s: 5.5.0
Resolution: Fixed
Fixed with svn revision 999924.
Now it's possible to configure custom broker id in the config file, like
<broker xmlns="http://activemq.apache.org/schema/core"; brokerName="brokerA"
brokerId="brokerA">
</broker>
This will ensure that broker always has the same broker id and prevent problems
with duplicate routes in network when broker is restarted.
Extra caution is needed to avoid having multiple brokers with the same ID.
> Implement custom brokerId assignment strategy
> ---------------------------------------------
>
> Key: AMQ-2927
> URL: https://issues.apache.org/activemq/browse/AMQ-2927
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.4.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.5.0
>
>
> In network of brokers, duplicate route detection is done by checking broker
> ids. After the restart, the broker ids change, which can cause duplicate
> routes and messages stuck due to reached ttl.
> We need to provide a mechanism for users to configure how their broker ids
> are assigned and make sure that they stay the same after the restart. Which
> will ensure correct duplicate route detection even after some of the broker
> in the mesh is restarted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
