I'm having the same problem.
I tried making my session façade stateless and afterwards statefull. The statefull-version worked faster, but gave the same exception when I tried to do 30 concurrent calls to the session façade (using threads).
I'm not that familiar with how the JRMP proxies work, but you might try this.
Get a browser up and goto http://127.0.0.1:8082
In there you'll see service=Naming and service=WebServer or something similar.
Both have the property backlog=50 by default.
Try raising this to 100+
If that works, you can change this forever in
depending on which version JBoss you are running.
Thanks for your reply.
I tried setting the backlog in the naming-service to 100 and afterwards to 500, with no effect.
I'm running JBoss 2.4.1 and I even took over the whole standard stateless-session-bean configuration, replacing the min-and max-size of the instance-pool to resp. 100 and 500.
But as even the statefull-version has the same problem, I guess it has nothing to do with the size of the instance-pool.
I don't see why it works perfectly with 20 concurrent threads running the same test, and not with 30+ concurrent threads.
Making such concurrent calls by the same client should be a situation which is common in Tomcat-JBoss-configurations.
Or is it just too demanding to want to access my session-bean by 30 threads concurrently?
Are you using windows as well?
I tried this on my Windows XP machine and got the same problem.
Most I got to start was 52 out of 100
I did get 98 out 100 by putting some sleeps in my client code.
When I tried it on my linux box I got no errors, all my connections were successful. The backlog is still set at 50.
Looks like a configuration problem in the Windows IP stack.
I have no idea how to fix it?
Note: This is a guess.
Hi, me again
It gets harder and harder to find stuff on the net every day :-(
I found this link about dynamic backlogging in Winsock
I haven't tried it myself, so NO WARRANTY :-)
Make sure you understand the consequences of this before changing it.
Hi there ...
... many thanks for your friendly help.
But unfortunately the problem still isn't solved ...
(like Homer Simpson would say) d'ooooooohhhhhh!!! ...
Have a nice day.
thanks for your reply.
I am using both Windows NT 4.0 and Windows 2000.
I have set the linux-test on my schedule for today ;)
I will post the results shortly.
C-ker aka Bart
Woehoew! I just ran my test on Redhat 7.1 on a 733Mhz with 100 concurrent clients and you had to see it going ;)!
No more exceptions!
I guess few people use Windows as a platform for JBoss for heavy-load-purposes ;)
Thanks a lot!
If I can help you some day: firstname.lastname@example.org