3 Replies Latest reply on Oct 10, 2002 4:07 AM by Stefan Jurk

    Trouble with IOR: for Naming

    Stefan Jurk Newbie

      Hello -
      we get an IOR: for Naming form JBoss 3.0.2 which runs on a localhost here (IOR is attached at the end).

      But when we want to access this from a client (using com.sun.jndi.cosnaming.CNCtxFactory), we get

      Exception in thread "main" org.omg.CORBA.INV_OBJREF: minor code: 1398079490
      at com.sun.corba.se.internal.core.CodeSetComponentInfo.read(CodeSetComp
      at com.sun.corba.se.internal.core.Profile.(Profile.java:114)
      [...]

      What is this funny minor code?? If we assume it is 1 (but what is 398079490??), then acc'g to the Javadoc "An IOR with no profile was encountered." How can JBoss emit such an IOR???

      Scared shitlessly ...

      St.Jurk/H.M.Mueller

      -----

      Here is the full stacktrace:


      Exception in thread "main" org.omg.CORBA.INV_OBJREF: minor code: 1398079490
      at com.sun.corba.se.internal.core.CodeSetComponentInfo.read(CodeSetComp
      at com.sun.corba.se.internal.core.Profile.(Profile.java:114)
      at com.sun.corba.se.internal.core.IOR.getProfile(IOR.java:278)
      at com.sun.corba.se.internal.iiop.CDRInputStream.read_Object(CDRInputSt
      at com.sun.corba.se.internal.iiop.CDRInputStream.read_Object(CDRInputSt
      at com.sun.corba.se.internal.corba.ORB.string_to_object(ORB.java:1075)
      at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:279)
      at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:218)
      at com.sun.jndi.cosnaming.CNCtx.(CNCtx.java:73)
      at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.j
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:24
      at javax.naming.InitialContext.init(InitialContext.java:222)
      at javax.naming.InitialContext.(InitialContext.java:178)

      -----

      Here is the IOR from the JBoss3 server.log:

      IOR:000000000000002B49444C3A6F6D672E6F72672F436F734E616D696E672F4E616D696E67436F6E746578744578743A312E300000000000020000000000000068000102000000000D3137322E31362E31352E363000000DC8000000114A426F73732F4E616D696E672F726F6F74000000000000020000000000000008000000004A414300000000010000001C00000000000100010000000105010001000101090000000105010001000000010000002C0000000000000001000000010000001C00000000000100010000000105010001000101090000000105010001

        • 1. Re: Trouble with IOR: for Naming
          Francisco Reverbel Novice

          Hi,

          This is a known issue. The minor code you posted indicates
          you are using Sun's 1.3 ORB at the client side. This ORB is buggy. A workaround is to use JacORB at the client side. Pass to your client a command line switch like

          -Xbootclasspath/p:$JBOSS_HOME/client/jacorb.jar

          If you cannot use JacORB at the client side, try Sun's 1.4 ORB or IBM's 1.3.1 ORB.

          BTW, the IOR you posted is good. I've just run an IOR parsing utility on it. Here is the output:

          ------IOR components-----
          TypeId : IDL:omg.org/CosNaming/NamingContextExt:1.0
          TAG_INTERNET_IOP Profiles:
          Profile Id : IIOP Version : 1.2
          Host : 172.16.15.60
          Port : 3528
          Object key (URL): JBoss/Naming/root
          Object key (hex): 0x4A 42 6F 73 73 2F 4E 61 6D 69 6E 67 2F 72 6F 6F 74
          -- Found 2 Tagged Components--
          #0: TAG_ORB_TYPE
          Type: 1245790976 (JacORB)
          #1: TAG_CODE_SETS
          ForChar native code set Id: ISO 8859-1
          Char Conversion Code Sets: UTF-8
          ForWChar native code set Id: UTF-16
          WChar Conversion Code Sets: UTF-8

          Components in MULTIPLE_COMPONENTS profile: 1
          #0: TAG_CODE_SETS
          ForChar native code set Id: ISO 8859-1
          Char Conversion Code Sets: UTF-8
          ForWChar native code set Id: UTF-16
          WChar Conversion Code Sets: UTF-8


          Regards,

          Francisco

          • 2. Re: Trouble with IOR: for Naming
            Francisco Reverbel Novice

            Hi,

            (Already replied to this thread but my reply didn't show up... Trying again.)

            The INV_OBJREF exception with minor code 1398079490 is a known issue. It happens whenever you attempt to use Sun's 1.3.x ORB at the client side. This ORB is buggy.

            The recommended workaround is to use JacORB 1.4.1 at the client side. Pass to you client a command line switch like

            -Xbootclasspath/p:$JBOSS_HOME/client/jacorb.jar

            If you cannot use JacORB at the client side, try Sun's
            1.4 ORB or IBM's 1.3 ORB.

            BTW, the IOR you have posted is good. I've just run an IOR parsing utility on it. Here is the output:

            ------IOR components-----
            TypeId : IDL:omg.org/CosNaming/NamingContextExt:1.0
            TAG_INTERNET_IOP Profiles:
            Profile Id : IIOP Version : 1.2
            Host : 172.16.15.60
            Port : 3528
            Object key (URL): JBoss/Naming/root
            Object key (hex): 0x4A 42 6F 73 73 2F 4E 61 6D 69 6E 67 2F 72 6F 6F 74
            -- Found 2 Tagged Components--
            #0: TAG_ORB_TYPE
            Type: 1245790976 (JacORB)
            #1: TAG_CODE_SETS
            ForChar native code set Id: ISO 8859-1
            Char Conversion Code Sets: UTF-8
            ForWChar native code set Id: UTF-16
            WChar Conversion Code Sets: UTF-8

            Components in MULTIPLE_COMPONENTS profile: 1
            #0: TAG_CODE_SETS
            ForChar native code set Id: ISO 8859-1
            Char Conversion Code Sets: UTF-8
            ForWChar native code set Id: UTF-16
            WChar Conversion Code Sets: UTF-8

            Cheers,

            Francisco

            • 3. Re: Trouble with IOR: for Naming
              Stefan Jurk Newbie

              Hi Francisco!
              thanks for your help. We've solved our problem now with an extra indirection layer using JacOrb as a standalone ORB. But I try this out too!
              Did you recognize, that the client of testsuite example "helloiiop" seems to use the "standard" jndi.properties and not the "corba" jndi.properties?

              Stefan