5 Replies Latest reply on Mar 1, 2005 12:07 AM by sanjewad

    RMI+SSL Invoker bug in jboss 3.2.1?

    jarikr Newbie

      Hi,

      I encoutered the following problem when I tried the example of chap8/ex4 of the pay-doc using JBoss 3.2.1 - it simply ignores the entries I put into the jboss.xml:

      <home-invoker>jboss:service=invoker, type=jrmp,socketType=SSL</home-invoker>
      <bean-invoker>jboss:service=invoker, type=jrmp,socketType=SSL</bean-invoker>


      Even if I haven't installed the SSL invoker, it deploys and can be called by any client without using SSL. I tried the example also with JBoss 3.0.6 where it worked as described in the pay-doc (the EJB deployment fails if I haven't installed the invoker). Has anything changed in the new JBoss or did anyone have the same problem?

      thanks for any hint in advance,
      Jari

      P.S.: I also tried the HTTPInvoker which was ignored, too.

        • 1. Re: RMI+SSL Invoker bug in jboss 3.2.1?
          jarikr Newbie

          After checking out the change log, standardjboss.xml and the jboss_3_2.dtd I figured out that the invoker configuration changed, so the jboss.xml has to look like this:



          <invoker-proxy-bindings>

          <invoker-proxy-binding>
          stateless-rmi-ssl-invoker
          <invoker-mbean>jboss:service=invoker,type=jrmp,socketType=SSL</invoker-mbean>
          <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>

          <proxy-factory-config>

          <client-interceptors>


          org.jboss.proxy.ejb.HomeInterceptor
          org.jboss.proxy.SecurityInterceptor
          org.jboss.proxy.TransactionInterceptor
          org.jboss.invocation.InvokerInterceptor



          org.jboss.proxy.ejb.StatelessSessionInterceptor
          org.jboss.proxy.SecurityInterceptor
          org.jboss.proxy.TransactionInterceptor
          org.jboss.invocation.InvokerInterceptor

          </client-interceptors>
          </proxy-factory-config>
          </invoker-proxy-binding>
          </invoker-proxy-bindings>

          <enterprise-beans>


          <ejb-name>EchoBean4</ejb-name>
          <configuration-name>SSL Stateless SessionBean</configuration-name>


          </enterprise-beans>

          <container-configurations>

          <container-configuration extends="Standard Stateless SessionBean">
          <container-name>SSL Stateless SessionBean</container-name>
          <invoker-proxy-binding-name>stateless-rmi-ssl-invoker</invoker-proxy-binding-name>
          </container-configuration>
          </container-configurations>


          That's it. Why don't you guys open a forum for the migration from JBoss 3 to JBoss 3.2?

          • 2. Re: RMI+SSL Invoker bug in jboss 3.2.1?
            Juha Lindfors Master

            > That's it. Why don't you guys open a forum for the
            > migration from JBoss 3 to JBoss 3.2?

            I'll collect any documents concerning migration between different JBoss versions to the FAQ forum. Please submit there.

            -- Juha

            • 3. Re: RMI+SSL Invoker bug in jboss 3.2.1?
              kevinp Newbie

              I tried to get the invoker running as you suggested about, however I am sitill unable to get an SSL connection. I have been able to get an SSL connection whern I overrode just the JRMP default invoker. Howerver the one argument extra socketType=SSL is giving me a considerable headache.

              Coudl some please list in a methodical fashion how I would be able to get SSL working over RMI ?

              • 4. Re: RMI+SSL Invoker bug in jboss 3.2.1?
                Les Green Newbie

                Just thought I'd say THANKS!!!! I eventually found this posting after 1 1/2 days of frustrating searching around trying different things to get this to work!!!

                But that does it perfectly!!!

                Regards,

                Lynke

                • 5. Re: RMI+SSL Invoker bug in jboss 3.2.1?
                  sanjewad Newbie

                  Please send me the example you got it working. I am still having problem with RMI+SSL setup for JBoss 3.2.6