[jboss-user] [Remoting] - Re: ServerThread

ron.sigal@jboss.com do-not-reply at jboss.com
Wed Oct 10 18:43:08 EDT 2007


Hi Poyan,

The Remoting bisocket transport used by JBossMessaging has a second ServerSocket on the server which has to be accessible.  Bisocket was designed for the use case in which the client was behind a firewall but the server was not, and the second ServerSocket used a random port.  Since Remoting version 2.2.2.GA, the second port has been configurable: see JIRA issue JBREM-749 "BisocketServerInvoker: Make configurable the address and port of secondary server socket" (http://jira.jboss.com/jira/browse/JBREM-749.

The remoting jar (jboss-remoting.jar) for version 2.2.2.GA (or later - the most current release is 2.2.2.SP2) is available from http://repository.jboss.com/jboss/remoting/.  You need to put the jar in the lib directory of your particular server configuration:  e.g., $JBOSS_HOME/server/messaging/lib.

Also, you need to configure the secondary port in server/messaging/deploy/jboss-messaging.sar/remoting-bisocket-service.xml. For example, to set the secondary port to 5445, add the secondaryBindPort attribute as follows:


  |    <mbean code="org.jboss.remoting.transport.Connector"
  |           name="jboss.messaging:service=Connector,transport=bisocket"
  |           display-name="Bisocket Transport Connector">
  |       <attribute name="Configuration">
  |          <config>
  |             <invoker transport="bisocket">
  |                <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
  |                <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
  |                <attribute name="dataType" isParam="true">jms</attribute>
  |                <attribute name="socket.check_connection" isParam="true">false</attribute>
  |                <attribute name="timeout" isParam="true">0</attribute>
  |                <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
  |                <attribute name="serverBindPort">4457</attribute>
  |                <attribute name="leasePeriod">10000</attribute>
  |                <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
  |                <attribute name="serverSocketClass" isParam="true">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
  |                <attribute name="numberOfRetries" isParam="true">1</attribute>
  |                <attribute name="numberOfCallRetries" isParam="true">1</attribute>
  |                <attribute name="clientMaxPoolSize" isParam="true">50</attribute>
  |                <attribute name="secondaryBindPort">5445</attribute>
  |             </invoker>
  |             <handlers>
  |                <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
  |             </handlers>
  |          </config>
  |       </attribute>
  |    </mbean>
  | 

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

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



More information about the jboss-user mailing list