-
1. Re: Too many channels open / No EJB receiver available for handling
als Mar 27, 2013 9:50 AM (in response to eminil)Exactly same issue we got. We use a WAR application in tomcat, each request is creating a static IntialContext object and the next request is closing the previous one of it and creating a new one.
same thing- "too many channels open".
-
2. Re: Too many channels open / No EJB receiver available for handling
mohaidriss Feb 14, 2014 10:54 AM (in response to als)I had exactly the same problem.
The solution I adopted was to make use of context.close().
See this post below.
-
3. Re: Too many channels open / No EJB receiver available for handling
ctomc Feb 14, 2014 1:40 PM (in response to mohaidriss)it is a bug in your client code, there ware many threads on this subject on this forum
you should be closing initial context for example.
-
4. Re: Too many channels open / No EJB receiver available for handling
wdfink Feb 15, 2014 3:58 PM (in response to mohaidriss)It depends on your client side code (which approach you use)
You should read the documentation EJB invocations from a remote client using JNDI (wildFly is ok for this and contain the latest informations)
If you can't get it to work you should open a new thread and provide more details about your client approach