3 Replies Latest reply on Aug 2, 2005 2:10 PM by Bill Burke

    EJB3 via HTTP invoker

    Mikhail Garber Newbie

      I would like to deploy my EJB3 session bean in a way to make it accessible remotely via HTTP (including JNDI lookup).

      I added http-invoker.sar to the deploy dir and modified ejb3.deployer/META-INF/jboss-server.xml replacing:

       <mbean code="org.jboss.remoting.transport.Connector"
       xmbean-dd="org/jboss/remoting/transport/Connector.xml"
       name="jboss.remoting:type=Connector,transport=socket3873,handler=ejb3">
       <depends>jboss.aop:service=AspectDeployer</depends>
       <attribute name="InvokerLocator">socket://0.0.0.0:3873</attribute>
       <attribute name="Configuration">
       <handlers>
       <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
       </handlers>
       </attribute>
       </mbean>
      


      with

      <mbean code="org.jboss.remoting.transport.Connector"
       xmbean-dd="org/jboss/remoting/transport/Connector.xml"
       name="jboss.remoting:service=Connector,transport=HTTP"
       display-name="HTTP transport Connector">
       <depends>jboss.aop:service=AspectDeployer</depends>
      
       <attribute name="InvokerLocator">http://0.0.0.0:8080/invoker/EJBInvokerServlet</attribute>
      
       <attribute name="Configuration">
       <config>
       <handlers>
       <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
       </handlers>
       </config>
       </attribute>
       </mbean>
      
      


      The resulting config gives me "Address already in use: JVM_Bind:8080" while deploying jmx-console.war but otherwise starts ok. When I try to connect from remote client using org.jboss.naming.HttpNamingContextFactory and java.naming.provider.url=http://servername:8080/invoker/JMXInvokerServlet, it is just hanging there and nothing happens.

      Any pointers would be greately appreciated.