[jboss-user] [Remoting] - Re: Remoting via mbean issue

[tom.elrod@jboss.com]

I just did a checkout of JBossRemoting (tag remoting_2_0_0_GA) and built the jboss-remoting.jar and jboss-remoting-tests.jar (this jar contains the MBeanHandler classes) using the tests.jars ant target.  Then copied both jars into server/default/lib directory of JBossAS 4.0.4.GA.  Then created a mbeanhandler-service.xml containing following and put in deploy directory:


  | <?xml version="1.0" encoding="UTF-8"?>
  | <!DOCTYPE server>
  | 
  | <!-- ======================================================== -->
  | <!-- Example JBoss Remoting Service Configuration file        -->
  | <!-- ======================================================== -->
  | <server>
  | 
  |    <!-- NOTE: set this up to the path where your libraries are -->
  |    <classpath codebase="lib"
  |       archives="*"/>
  | 
  |    <mbean code="org.jboss.remoting.network.NetworkRegistry"
  |       name="jboss.remoting:service=NetworkRegistry"/>
  | 
  |    <!-- MBean Server Invocation Handler -->
  |    <mbean code="org.jboss.test.remoting.handler.mbean.MBeanHandler"
  |       name="test:type=handler"/>
  | 
  | 
  |    <mbean code="org.jboss.remoting.transport.Connector"
  |       name="jboss.remoting:service=Connector,transport=Socket"
  |       display-name="Socket transport Connector">
  | 
  |       <!-- Can either just specify the InvokerLocator attribute and not the invoker element in the -->
  |       <!-- Configuration attribute, or do the full invoker configuration in the in invoker element -->
  |       <!-- of the Configuration attribute. -->
  | 
  |       <!-- Remember that if you do use more than one param on the uri, will have to include as a CDATA, -->
  |       <!-- otherwise, parser will complain. -->
  |       <!--       <attribute name="InvokerLocator"><![CDATA[socket://${jboss.bind.address}:8084/?enableTcpNoDelay=false&clientMaxPoolSize=30]]></attribute>-->
  | 
  |       <attribute name="Configuration">
  |          <config>
  |             <invoker transport="socket">
  |                <attribute name="numAcceptThreads">1</attribute>
  |                <attribute name="maxPoolSize">303</attribute>
  |                <attribute name="clientMaxPoolSize" isParam="true">304</attribute>
  |                <attribute name="socketTimeout">60000</attribute>
  |                <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
  |                <attribute name="serverBindPort">5400</attribute>
  |                <!--              <attribute name="clientConnectAddress">216.23.33.2</attribute> -->
  |                <!--              <attribute name="clientConnectPort">7777</attribute> -->
  |                <attribute name="enableTcpNoDelay" isParam="true">false</attribute>
  |                <attribute name="backlog">200</attribute>
  |             </invoker>
  |             <handlers>
  |                <handler subsystem="test">test:type=handler</handler>
  |             </handlers>
  |          </config>
  |       </attribute>
  | 
  |    </mbean>
  | 
  | 
  | </server>
  | 
  | 

Then ran the org.jboss.test.remoting.handler.mbean.ClientTest under the jboss remoting project and everything worked.

The only thing I saw based on what you posted is that your mbeanhandler-service.xml file should not have deployed with remoting 2.0.0.GA because your Connector mbean contained the following:


  | xmbean-dd="org/jboss/remoting/transport/Connector.xml"
  | 

So I'm guessing either the service deployment failed or are not really using remoting 2.0.0 jar file.  May also want to verify your client is also using 2.0.0 jar.

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

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