The solution in JBEAP-13199 worked around an underlying bug in remoting which causes shared uses of a connection to hang it the case that connection establishment fails. The shared handles never receive a notification.
While JBEAP-13199 worked around the problem, there is still the potential that another code path could hit this problem, so a patch was made to correct the underlying issue. That change is reflected in REM3-315
- incorporates
-
REM3-315 ConnectionInfo.MaybeShared#getConnection returns a non-completing future with non-matching auth configs
-
- Resolved
-
- is incorporated by
-
JBEAP-13550 Upgrade JBoss Remoting to 5.0.5.Final
-
- Verified
-
- relates to
-
EJBCLIENT-285 Reuse seed connection auth config for cluster topology created connections
-
- Resolved
-
