+++ This bug was initially created as a clone of Bug #1056216 +++ Cluster connection bridge should use the "reconnect-attempts" value for both the initial connection attempts and reconnection attempts. --- Additional comment from on 2014-01-21 14:25:55 EST --- Fix committed to the 2.3.x branch. See https://github.com/hornetq/hornetq/commit/8ef706763c784aebc43c1b4aa3dfc309122f5f2d. --- Additional comment from Kabir Khan on 2014-04-04 10:46:11 EDT --- Setting to ON_QA since upgrade should fix this
Fix is not present in HornetQ tag HornetQ_2_3_14_1_Final which is in EAP 6.2.3.CP.ER2. (It seems that it was merged just to master but not to 2.3.x branch.) This fix also requires update of xsd schema so attribute "initial-connect-attempts" can be set in standalone...xml and domain.xml.
Ignore my comment above. Setting as verified. Attribute "reconnect-attempts" defines initial retry.
Refactored Doc Text to reflect Bug Fix resolution. Including original below should older details be required. Consequence : HornetQ could get in an infinite loop when trying to connect to a cluster node if it was disconnected during its initial connection attempt. Cause :This could be an issue in two cases: Using a static cluster configuration, any initial connect attempt would be done infinitely ignoring the number of retries parameter. Using a dynamic cluster configuration, if the node was disconnected between the time it received a notification about the node being part of the cluster topology and the initial connection. In any of these cases an infinite loop trying to connect would be in place wasting CPU resources. Fix: Cluster connection bridge should use the "reconnect-attempts" value for both the initial connection attempts and reconnection attempts. Result: HornetQ infinite loop avoided.