-
Bug
-
Resolution: Done
-
Major
-
7.3.7.GA
-
False
-
False
-
-
-
-
-
-
-
-
Undefined
-
A race condition in RemotingEJBDiscoveryProvider is causing a NullPointerException in line 126 during autoboxing the Long value.
This can happen in the case that Thread A is executing line 123 with the containsKey and a return value of true, then Thread B is removing that entry from the Map, while Thread A is calling get in line 126, which will result in a return value of null, leading to a NullPointerException during autoboxing, see:
122 private boolean haveNotExpiredFailedDestination(URI uri) { 123 if(!failedDestinations.containsKey(uri)) 124 return false; 125 else { 126 long failureTimestamp = failedDestinations.get(uri); 127 long delta = System.nanoTime() - failureTimestamp; 128 return delta < DESTINATION_RECHECK_INTERVAL; 129 } 130 }
- clones
-
JBEAP-22152 [GSS](7.4.z) EJBCLIENT-408 - Racecondition in RemotingEJBDiscoveryProvider is causing a NullPointerException
- Closed
- is incorporated by
-
JBEAP-22154 [GSS](7.2.z) Racecondition in RemotingEJBDiscoveryProvider is causing a NullPointerException
- Closed
-
JBEAP-22343 [GSS](7.3.z) Upgrade jboss-ejb-client from 4.0.39.SP1-redhat-00001 to 4.0.43.Final-redhat-00001
- Closed