1 2 Previous Next 21 Replies Latest reply on May 27, 2004 12:46 PM by themuppeteer Go to original post
      • 15. Re: JMS over HTTP with server behind a firewall problem
        catalean

        I think You have to enable a HTTP detached invoker on your EJBs. You better search for more information about detached invokers in JBoss. I just found this example, i did't test it yet, but it seems to be the solution for your, and also, for my problem to. You have to modify your jboss.xml descriptor, and for each EJB you want to access over HTTP, specify the http detached invoker. Then you obtain the home interface of an EJB, looking up after the jndi name specified by the invoker binding, "helloworld/HelloHTTP". Hope it helps.

        <?xml version="1.0" encoding="UTF-8"?>
        <!DOCTYPE jboss PUBLIC
         "-//JBoss//DTD JBOSS 3.2//EN"
         "http://www.jboss.org/j2ee/dtd/jboss_3_2.dtd">
        
        <jboss>
         <enterprise-beans>
         <session>
         <ejb-name>HelloWorld</ejb-name>
         <jndi-name>helloworld/Hello</jndi-name>
         <invoker-bindings>
         <invoker>
         <invoker-proxy-binding-name>stateless-http-invoker</invoker-proxy-binding-name>
         </invoker>
         <jndi-name>helloworld/HelloHTTP</jndi-name>
         </invoker-bindings>
         </session>
         </enterprise-beans>
        
         <invoker-proxy-bindings>
         <!-- A custom invoker for RMI/HTTP -->
         <invoker-proxy-binding>
         <name>stateless-http-invoker</name>
         <invoker-mbean>jboss:service=invoker,type=http</invoker-mbean>
         <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
         <proxy-factory-config>
         <client-interceptors>
         <home>
         <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
         <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
         <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
         <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
         </home>
         <bean>
         <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor>
         <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
         <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
         <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
         </bean>
         </client-interceptors>
         </proxy-factory-config>
         </invoker-proxy-binding>
         </invoker-proxy-bindings>
        </jboss>


        • 16. Re: RMI over HTTP , hostname appears in client instead of ip

           

          "themuppeteer" wrote:

          I don't use JMS


          Why are you posting in the JMS forum then?


          • 17. Re: JMS over HTTP with server behind a firewall problem
            themuppeteer

            Sorry for that Adrian,
            I found this link by using google. I think the problem is more general then only JMS. Anyway, the solution to cataleans problem is the same as for my problem and thats why I'm on this thread.

            Catalean,
            I'll try this tonight and post the result. Hope it works.

            • 18. Re: JMS over HTTP with server behind a firewall problem
              themuppeteer

              hmm no succes... don't even find my bean.

              Catalean, may I ask how you layed the connection to the detached http invoker from the 'unknownHostException' ?
              If I google on 'detached http invoker hostname' I get nothing.

              Wouldn't there be a way to 'set' the ip correctely after we got the home interface ? So before calling the create we could correct the servers url ?
              The client does know the ip of the server, so why can't he use it then ?

              • 19. Re: JMS over HTTP with server behind a firewall problem
                catalean

                Little correction, sorry for that, the following is wrong:

                <invoker-bindings>
                 <invoker>
                 <invoker-proxy-binding-name>stateless-http-invoker</invoker-proxy-binding-name>
                 </invoker>
                 <jndi-name>helloworld/HelloHTTP</jndi-name>
                 </invoker-bindings>

                This is correct:
                <invoker-bindings>
                 <invoker>
                 <invoker-proxy-binding-name>stateless-http-invoker</invoker-proxy-binding-name>
                 <jndi-name>helloworld/HelloHTTP</jndi-name>
                 </invoker>
                 </invoker-bindings>

                It also works, the bean's home is found looking up after "helloworld/HelloHTTP".

                • 20. Re: JMS over HTTP with server behind a firewall problem
                  themuppeteer

                  I'm getting 'bean not bound' , guess I'll search on that first.
                  Does everything work for you now catalean ?
                  Can you do a create on your beans home without exceptions ?

                  • 21. Re: JMS over HTTP with server behind a firewall problem
                    themuppeteer

                    IT WORKS!!!!!

                    Thanks a million catalean!

                    1 2 Previous Next