-
Bug
-
Resolution: Done
-
Major
-
1.2.1.Final
-
None
-
False
-
None
-
False
-
-
Currently successful discovery by any of the nodes leads to cancellation of all other discovery attempts. In some circumstances this may lead to the problems see WFDISC-53 or EJBCLIENT-492.
OTOH, performing discovery cancellation should not be necessary - we can just let other attempts to finish and populate their caches so that they can be later used.
- causes
-
EJBCLIENT-492 Discovery: make sure request cancellation doesn't cause ConcurrentModificationException
- Resolved
-
WFDISC-53 Node starvation is possible if time to establish connection is non-negligible
- Resolved
- is incorporated by
-
JBEAP-26684 [GSS](7.4.z) WFDISC-54 - EJB discovery: when LDAP dir-context is used in cluster only deployments from one node are being discovered
- Closed
-
JBEAP-26719 (8.0.z) WFDISC-54 - EJB discovery: when LDAP dir-context is used in cluster only deployments from one node are being discovered
- Closed