[jboss-user] [Remoting] - Re: Socket keep alive with client EJB
ron.sigal@jboss.com
do-not-reply at jboss.com
Mon Jan 5 19:34:44 EST 2009
Ah, yes, you're quite right about ejb3-connectors-service.xml, which introduces two new things:
1. the new Remoting configuration method, using the org.jboss.remoting.ServerConfiguration object, and
2. the ServiceBindingManager.
The ServerConfiguration doesn't play a big role in ejb3-connectors-service.xml, though a more extensive example can be found in .../deploy/remoting-jboss-beans.xml, which replaces the Remoting configuration that used to be in conf/jboss-service.xml. More information about ServerConfiguration can be found in Section 5.1.1.3. "Declarative configuration: POJOs" of the Remoting Guide (http://www.jboss.org/jbossremoting/docs/guide/2.5/html/index.html).
The updated ServiceBindingManager, which makes it easy to configure ports for the various services, is discussed in the wiki at http://www.jboss.org/community/docs/DOC-9038.
In any case, despite the changes, the InvokerLocator is given explicitly, just as it used to be in .../deploy/ejb3.deployer/jboss-service.xml:
| <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}</parameter>
| <parameter>
| <null />
| </parameter>
| <parameter>3873</parameter>
| </value-factory>
|
| </property>
|
Just change
| <parameter>socket://${jboss.bind.address}:${port}</parameter>
|
to
| <parameter>socket://${jboss.bind.address}:${port}/?timeout=12345</parameter>
|
"slimamar" wrote :
| In the documentation, there is this :
| "You can configure JBoss Remoting through the JBoss Messaging service configuration file JBOSS_HOME/server/<your_configuration>/deploy/messaging/remoting-service.xml."
| But this file doesn't exist and does reference to 'messaging'.
|
That sounds like something that should be fixed. Where did you see it?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199647#4199647
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199647
More information about the jboss-user
mailing list