WebSphere & RMI/IIOP

[David Agren]

I am trying to make a connection between a servlet running under
WebSphere (version 3.0.2.1, advanced edition, IBM JDK 1.1.8, Windows NT
4.0) and a remote application (written in Java 1.3, registered with the
tnameserv ORB provided as part of the Sun JDK 1.3).

I'm using the following code to retrieve the remote interface:

private static Object getInterfaceObj(String objName, Class cl, String
host, String id, String port)
throws NamingException
{
Hashtable init = new Hashtable();
init.put("java.naming.factory.initial",
"com.ibm.ejs.ns.jndi.CNInitialContextFactory");
init.put("java.naming.provider.url", "iiop://" + host + ":" + port);

InitialContext context = new InitialContext(init);
return PortableRemoteObject.narrow(context.lookup(objName + id), cl);
}

Sadly, instead of a connection we get the following error message:

[Root exception is org.omg.CORBA.BAD_PARAM: minor code: 0 completed:
No]javax.naming.ServiceUnavailableException
at java.lang.Throwable.(Throwable.java:63)
at java.lang.Exception.(Exception.java:28)
at javax.naming.NamingException.(NamingException.java:131)
at
javax.naming.ServiceUnavailableException.(ServiceUnavailableException.java:63)

at
com.ibm.ejs.ns.jndi.CNInitialContextFactory.initRootContext(CNInitialContextFactory.java:416)

at
com.ibm.ejs.ns.jndi.CNInitialContextFactory.getInitialContext(CNInitialContextFactory.java:189)

at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:783)

at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:165)
at javax.naming.InitialContext.(InitialContext.java:142)
at com.maila.lim.BridgeToMEN.getInterfaceObj(BridgeToMEN.java:35)

My code is working when tested with another servlet engine (Tomcat).
The question is, obviously, what we're doing wrong on WebSphere and how
to make it work.
Is this a known problem with WebSphere's ORB or I'm I doing something
wrong in my code?

Best Regards,
David Agren
Brainpool Consulting AB

[Randy Schnier]

It's not a problem with the ORB, per se, but a mismatch of ORB versions within the JDKs. WebSphere
3.0.2.x supports only IBM's JDK 1.1.7 (on client and server). WebSphere 3.5 will support only
IBM's JDK 1.2.2 (on client and server). Other JDK versions may work, but are not supported. This
is due to the amount of testing required to guarantee robustness and stability couplied with the
number of permutations that are possible. (For what it's worth, I don't believe the ORBs in Sun's
JDK 1.1.x and 1.2.x are generally interoperable either.)

WebSphere 3.0.2.1 and WebSphere 3.5 servers will be interoperable, subject to the conditions above.

David Agren wrote:

--
Randy Schnier

[Billy Newport]

There is a tip on using JDK 1.2.2 with WAS 3.02 at http://www.ejbinfo.com.
Tested with Session beans.

--
==============================================
Find help on using WebSphere at http://www.ejbinfo.com
==============================================

"David Agren" <david...@brainpool.se> wrote in message
news:3973315F...@brainpool.se...

[BOSS GmbH, Andreas Nagel]

I was excited to read, that it seems to be possible to run a JDK 1.2.2
client application with WAS 3.02. Thats what I we are looking for. It is
very important for us to make this run.

So, I downloaded the rmi-iiop, installed it and run the checkme.bat without
errors.
But our application throws the attached exception!

Any ideas?

Regards,
Andreas

"Billy Newport" <billyn...@iname.com> schrieb im Newsbeitrag
news:8li1vh$efu$1...@news.software.ibm.com...

[Billy Newport]

It only works with JDK 1.2.2-001. Sun changed the ORB in 1.2.2-004 with the
result that you get this exception now.

--
==============================================
Find help on using WebSphere/WebLogic at http://www.ejbinfo.com
==============================================

"BOSS GmbH, Andreas Nagel" <Nagel....@t-online.de> wrote in message
news:8loq1m$u3s$1...@news.software.ibm.com...