[JBoss Remoting Users] - Re: J2EE remote client HTTP tunneling
by ron.sigal@jboss.com
"bwarren" wrote :
| Is JBoss Remoting the way to go here?
|
Well, as it happens, JBossRemoting is the way you've already gone. EJBs, EJB3s, and JBossMessaging connections all, by default, use JBossRemoting as their transport layer, each, again by default, with their own Remoting servers listening on ports other than 80. However, one of the primary design principles of Remoting is the ability to swap one Remoting transport for another. In your case, you can get closer to your goal with the servlet transport, in which all of the various proxies connect to a Remoting servlet, which then passes the invocations to the appropriate subsystem. Of course, you would need a servlet container (i.e., a JBossWeb (aka Tomcat) connector) listening on port 80. Can you do that? Or will the network powers open up, say, 8080 (the default JBossWeb port in the Application Server - see $JBOSS_HOME/server/$CONFIG/deploy/jboss-web.deployer/server.xml)?
The configuration details are given in the wiki entry "EJB, JMS and JNDI over HTTP with Unified Invoker" at http://www.jboss.org/community/wiki/EJBJMSandJNDIoverHTTPwithUnifiedInvoker.
What do you think?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258016#4258016
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258016
15 years, 2 months
[JBoss Remoting Users] - Re: Infinite lock in MicroSocketClientInvoker
by 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
15 years, 2 months