Failure during reconnect phase for the EJB client in multithread environments
Issue
-
We have noticed a problem with the JBoss EJB client, when the remote EJB is a SLSB deployed on a 4 node JBoss EAP cluster, and the client is a web application running on
WAS.After a failed EAP instance joins back in the cluster, the client creates a number of "ejb-client-cluster-node-connection-creation" threads. These threads eventually disappear,
after about a minute.The problem is, that we have found that in the forementioned circumstances (client on WAS, 4 remote nodes) more and more of these threads are created each time we
restart an EAP instance. After 5-6 restarts we see, more than 200 of these threads on the WAS.However, if we repeat the same test with only 2 EAP nodes instead of 4, we don't see this increase in the number of threads.
However, when we repeat the same test, but with 4 remote instances in the EJB cluster instead of two you can see with the same command that the number of created
threads is getting bigger and bigger every time a restarted node joins the cluster.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.3.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.