6 Replies Latest reply on Nov 16, 2005 12:51 PM by baptiste

    Remote JNDI lookup Confusion

    zurchman

      We recently ported a application to JBoss 3.2.7 (from 3.2.2/3) and had to resolve some JNDI issues having to do with the ENC.

      The application runs on several hosts. A jsp in the web tier on host A periodically collects information from the same EJB's on host A and host B by doing remote JNDI lookups specifying the name of the remote host.

      The problem is that the remote lookup on host B done from the web tier on host A running JBoss 3.2.7 appears to be returning the address of the EJB on host A.

      The same jsp deployed on hosts running JBoss 3.2.2/3 works correctly.

      This does not appear to be a network problem; the jsp throws Network exceptions if the remote host is not available.

      Any ideas on this?


        • 1. Re: Remote JNDI lookup Confusion
          zurchman

          The problem is that the application running on JBoss 3.2.7 can not access Remote EJB's deployed on JBoss 3.2.2/3 servers.

          Could this problem be due to a configuration conflict?

          Running a JNDI browser on each server turned up some discrepancies.

          These entries appear in the 3.2.2/3 server, and are missing from 3.2.7:

          +- invokers
           +- hostB
           +- iiop (org.jboss.invocation.iiop.IIOPInvoker)
           +- jrmp (org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy)
           +- pooled
           (org.jboss.invocation.pooled.interfaces.PooledInvokerProxy)
          +- jmx:hostB:rmi (org.jboss.jmx.adaptor.rmi.RMIAdaptorImpl)
          

          These are the jmx entries from 3.2.2/3:
          +- jmx
           +- invoker
           +- RMIAdaptor ($Proxy19)
           +- rmi
           +- RMIAdaptor (org.jboss.jmx.adaptor.rmi.RMIAdaptorImpl)
          

          And these are from 3.2.7:
          +- jmx
           +- invoker
           +- RMIAdaptor ($Proxy137,$Proxy137)
           +- rmi
           +- RMIAdaptor => {jmx/invoker/RMIAdaptor}
          



          • 2. Re: Remote JNDI lookup Confusion
            zurchman

            It's a bug in 3.2.7

            I managed to work around it by implementing a custom InvokerInterceptor as suggested in the Jira bug report:
            http://jira.jboss.com/jira/browse/JBAS-1442

            Thanks to darrani for identifying this as a bug.

            His post is at the end of this thread, which describes a similar issue:

            http://www.jboss.org/index.html?module=bb&op=viewtopic&t=65260

            • 3. Re: Remote JNDI lookup Confusion
              biswojit

              Hi All

              I am trying to update from jboss3.2.2 to jboss4.0.2
              but the Swing client can't get access to jboss AS-4.0.2 but it works fine with 3.2.2. It seems a JNDI problem...
              If anybody has got any idea please let me know

              Thanks

              • 4. Re: Remote JNDI lookup Confusion
                darranl

                Biswojit, Please start a new topic to ask your question.

                • 5. Re: Remote JNDI lookup Confusion
                  biswojit

                  Thanks darranl for your quick reply.
                  It has been posted with a new topic
                  "Problem in porting of Swing/ jboss app from Jboss-3.2.2 to JBoss-4.0.2".


                  • 6. Re: Remote JNDI lookup Confusion
                    baptiste

                    Hi, I just ran into this very problem with jboss 4.0.1.

                    I downloaded the fixed version from CVS (tagged 1.5.6.2) and managed to compile it into a new package. I tried to use this version by changing all references to org.jboss.invocation.InvokerInterceptor with <my package>.InvokerInterceptor in files jboss-service.xml and the likes.

                    Problem: the nice little testcase (avalaible at http://jira.jboss.com/jira/browse/JBAS-1548) stills fails! I ran it under jboss 4.0.2 and it passed, but I can't afford to switch to it now.

                    If anybody could help me in the process of changing the InvokerInterceptor for session beans, I'd be very grateful.
                    Thanks in advance!