Hey, vink, thanks for contributing. -Ron
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4213986#4213986
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4213986
___
jboss-user mailing
Did you tune the timeouts in the EJB connectors? If so, what did you change
that resolved this issue?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4210809#4210809
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4210809
Prior to 2.4.0.SP1, every call to SLSB was creating a socket; as a result
system run out of sockets it throws cannot connect exception.
I migrated to this version who claimed to solve this bug. Also this version
exposed an extra attribute invokerDestructionDelay, which is used for reusing
the
It is working now. I've changed to Remoting 2.4.0.SP1. But I need to tune
timeouts in EJB3 connector configuration.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197025#4197025
Reply to the post :
