Re: [jboss-user] [JBoss Remoting] - How to set timeout for method invocation?
by Ron Sigal
Ron Sigal [http://community.jboss.org/people/ron.sigal%40jboss.com] replied to the discussion
"How to set timeout for method invocation?"
To view the discussion, visit: http://community.jboss.org/message/551122#551122
--------------------------------------------------------------
Hi Jacek,
Note that I moved this thread to the Remoting users forum.
I'm not really sure what your question is. However, it seems that, on the one hand, you have successfully set the timeout value for JNDI lookups, but you want to speed up the connection failures you're showing in the stacktraces. Is that right? If so, then you can set the connection timeout value in one of the server configuration files. Which file to change depends on the version of the Application Server you are using. For AS 4, go to $JBOSS_HOME/server/$CONFIG/deploy/ejb3.deployer/META-INF/jboss-service.xml and add, for example, "timeout=60000" to the "InvokerLocator" attribute:
<attribute name="InvokerLocator">socket://${jboss.bind.address}:3873/?invokerDestructionDelay=5000&timeout=60000</attribute>
which will set the timeout for connections and invocations to one minute.
In AS 5, go to $JBOSS_HOME/server/$CONFIG/deploy/ejb3-connectors-jboss-beans.xml and do the same thing.
-Ron
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/551122#551122]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months
Re: [jboss-user] [JBoss Remoting] - Threads Hanging in MicroSocketClientInvoker.readVersion()
by Ron Sigal
Ron Sigal [http://community.jboss.org/people/ron.sigal%40jboss.com] replied to the discussion
"Threads Hanging in MicroSocketClientInvoker.readVersion()"
To view the discussion, visit: http://community.jboss.org/message/551112#551112
--------------------------------------------------------------
Hi Nathan,
Note that I moved this discussion to the JBossRemoting users forum.
There are two different phenomena in your stacktraces. The first one shows a client hanging, waiting for a response to an invocation, in this case the response to an invocation on an EJB3. The fact that it's hanging means that, for some reason, the server isn't supplying a result. Do you see anything going on in server.log?
The second stacktrace shows a worker thread sitting in a read() call, waiting for some work to do. It's perfectly natural.
A timeout value for both the client side read() and the server side read() can be configured on the server. Where you do the configuring depends on which subsystem you want to configure. For EJB3, for example, go to $JBOSS_HOME/server/$CONFIG/deploy/ejb3-connectors-jboss-beans.xml and add "timeout" to the "InvokerLocator" property. For example,
<property name="invokerLocator">
<value-factory bean="ServiceBindingManager" method="getStringBinding">
<parameter>
jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
</parameter>
<parameter>
<null />
</parameter>
<parameter>socket://${jboss.bind.address}:${port}/?timeout=60000</parameter>
<parameter>
<null />
</parameter>
<parameter>3873</parameter>
</value-factory>
would set the timeout to one minute on both the client and server side.
-Ron
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/551112#551112]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months