-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
12.0.0.Beta1
-
None
Seen in our clustering tests where remote EJB clients invoke beans on 4 servers in cluster, while each of those is being killed and restarted. This is done in sequence and there's plenty of time in between the kill/start/kill-another (1 minute).
In two ouf our tests, we saw a small number of clients hang at the end. The scenarios are:
jvmkill-dist-sync (36 clients)
shutdown-dist-sync (1 client)
The hangs are not related to any error or warning message on the server-side. There are ClosedChannelExceptions on the client side, but these seem to be unrelated as the numbers of clients reporting the exceptions are not the same (lower) as the numbers of hanging clients.
No thread dump as I didn't manage to reproduce yet.
Might be related to JBEAP-12074 or JBEAP-13169.
- relates to
-
WFLY-10150 EJB race condition can cause client to be in awaitResponse while server is done
- Resolved
-
WFLY-9482 ejb remote client hangs on undertow default worker pool exhaustion
- Open