[jboss-user] [JBoss Remoting Users] - Re: Infinite lock in MicroSocketClientInvoker

[ron.sigal@jboss.com]

Hi Mayank,

"mayankmit2002" wrote : 
  | I'am just unable to set the socket time out at the client end 
  | 

The timeout isn't set in the initial context call.  If you look in $JBOSS_HOME/server/$CONFIG/deploy/ejb3.deployer/META-INF/jboss-service.xml, you'll see the MBean definition 


  |    <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</attribute>
  |       <attribute name="Configuration">
  |          <handlers>
  |             <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
  |          </handlers>
  |       </attribute>
  |    </mbean>
  | 

If you add "timeout" to the InvokerLocator attribute, it will be used by the Remoting server defined by the MBean and also by all of its clients:


  |    <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/?timeout=10000</attribute>
  |       <attribute name="Configuration">
  |          <handlers>
  |             <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
  |          </handlers>
  |       </attribute>
  |    </mbean>
  | 

For more information about Remoting configuration, see Chapter 5 of the Remoting Guide: http://jboss.org/jbossremoting/docs/guide/2.2/html/index.html.

-Ron

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258010#4258010

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258010