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 socket connection for a given delay.
I've just added this attribute to the default configuration & my system is
running without any issues. This attribute is optional, you can just try this
new version of remoting.
<mbean code="org.jboss.remoting.transport.Connector"
|
name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
| <depends>jboss.aop:service=AspectDeployer</depends>
| <attribute
name="InvokerLocator">socket://${jboss.bind.address}:3873/?invokerDestructionDelay=5000</attribute>
| <attribute name="Configuration">
| <handlers>
| <handler
subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </attribute>
| </mbean>
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210911#4210911
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210911
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
