Well at least it shows up at the top of the Google list. :)
Anyone Seen This error? It seems to be affecting all our JBoss applications.
KAC
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4093919#4093919
Reply to the post :
I did post this issue first in the Installation, Configuration DEPLOYMENT
forum thinking it is a configuration issue. I can recreate the exception at a
certain transaction rate on windows. Now I am trying on Linux, and so far no
socket exceptions.
anonymous wrote : I'm curious though: what
This is an strange phenomenon. You've got sockets and server sockets shutting
down in four different places:
1. Remoting worker thread
2. Remoting bisocket SecondaryServerSocketThread
3. PooledInvoker
4. tomcat.
Whatever is going on is clearly independent of Remoting, since the latter two
