4 Replies Latest reply on Feb 23, 2005 5:58 AM by Sunil Arora

    Problem calling EJB using RMI/IIOP while providing IOR for N

    Alan Burton Newbie

      I'm trying to call a remote EJB deployed on JBoss 3.2.4 using RMI/IIOP. I reviewed the article located at http://www.jboss.org/developers/projects/jboss/IIOP. I was successful in calling the EJB using both corbaloc and IOR for the provider url when my client is compiled and run using JDK 1.4.2_04. However, when I use the IOR reference for the Corba Naming Service and compile and run my client using JDK 1.3.1_12 I get an org.omg.CORBA.INV_OBJREF exception.

      org.omg.CORBA.INV_OBJREF: minor code: 1398079490 completed: No
      at com.sun.corba.se.internal.core.CodeSetComponentInfo.read(CodeSetCompo
      at com.sun.corba.se.internal.core.Profile.(Profile.java:109)
      at com.sun.corba.se.internal.core.IOR.getProfile(IOR.java:273)
      at com.sun.corba.se.internal.iiop.CDRInputStream.read_Object(CDRInputStr
      at com.sun.corba.se.internal.iiop.CDRInputStream.read_Object(CDRInputStr
      at com.sun.corba.se.internal.corba.ORB.string_to_object(ORB.java:1079)
      at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:274)
      at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:213)
      at com.sun.jndi.cosnaming.CNCtx.(CNCtx.java:68)
      at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.ja
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241
      at javax.naming.InitialContext.init(InitialContext.java:217)
      at javax.naming.InitialContext.(InitialContext.java:193)
      at com.eircom.ea.EAAccess.testNeon(EAAccess.java:180)
      at com.eircom.ea.EAClient.main(EAClient.java:136)

      I am tied to using the JDK 1.3.x as I am calling the EJB from within a java stored procedure on an Oracle 9.2 database. I don't want to use RMI/JRMP as this requires the JBoss client jars to be loaded into the database. I believe there is a known bug with JDK 1.3.x concerning code set negotiations. The article referenced above seems to indicate that it is possible to have IIOP clients access beans remotely deployed on JBoss using the Naming service IOR. Does anyone have any additional information that might help me resolve this issue or a workaround for the problem?