-
Bug
-
Resolution: Done
-
Critical
-
2.1.0.Final
-
None
If "attemptReconnections" method of the EJBClientContext is called when there are no reconnection handlers available (it's quite common situation) the component is being left in the "attemptingReconnect" state forever so no reconnection is possible even if new reconnection handlers will become available later.
The second problem is that the array of reconnection handlers is not properly synchronized when it's copied to the new array.
Pull request available.