Meaningless Drivel is fun!
The moose likes Websphere and the fly likes Can't we access EJB's deployed on WebSphere from a non IBM JVM client? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Products » Websphere
Bookmark "Can Watch "Can New topic

Can't we access EJB's deployed on WebSphere from a non IBM JVM client?

Maruti Nori

Joined: Mar 13, 2002
Posts: 7

We ar usign IBM websphere for deploying our EJBs.But we are not able to access the EJB from any non IBM's JVM clients eventhough we place websphere.jar and j2ee.jar in the classpath.It gives the following exception.
java.lang.NoClassDefFoundError: com/ibm/rmi/iiop/ORB
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(
at Method)
at java.lang.ClassLoader.loadClass(
at sun.misc.Launcher$AppClassLoader.loadClass(
at java.lang.ClassLoader.loadClass(
at java.lang.ClassLoader.loadClassInternal(
at javax.naming.spi.NamingManager.getInitialContext(
at javax.naming.InitialContext.getDefaultInitCtx(
at javax.naming.InitialContext.init(
at javax.naming.InitialContext.<init>(
at javax.swing.AbstractButton.fireActionPerformed(
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Abstra
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel
at javax.swing.DefaultButtonModel.setPressed(
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonL
at java.awt.Component.processMouseEvent(
at java.awt.Component.processEvent(
at java.awt.Container.processEvent(
at java.awt.Component.dispatchEventImpl(
at java.awt.Container.dispatchEventImpl(
at java.awt.Component.dispatchEvent(
at java.awt.LightweightDispatcher.retargetMouseEvent(
at java.awt.LightweightDispatcher.processMouseEvent(
at java.awt.LightweightDispatcher.dispatchEvent(
at java.awt.Container.dispatchEventImpl(
at java.awt.Window.dispatchEventImpl(
at java.awt.Component.dispatchEvent(
at java.awt.EventQueue.dispatchEvent(
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchTh
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
at java.awt.EventDispatchThread.pumpEvents(
But if we change the path to point to IBM's JVM it works fine.
Does this mean that to connect to IBM webSphere we do not have any option other than
running the client from an IBM's JVM.
Max Tomlinson
Ranch Hand

Joined: Jul 17, 2001
Posts: 365
This used to be the case for earlier versions of the JVM--I've seen this problem is WAS 3.5 but heard it was supposed to be fixed by 4.0. I believe it has to do with RMI/IIOP.
Ian Moore

Joined: Jul 12, 2002
Posts: 4
I think this is to do as the previous post suggests with IBM's implementation of the RMI/IIOP stubs in that they're not compatible with the Sun implementation and hence you're problems. This was under VAJ 4 plus the RMI fix too.
Fortunately for me I no longer have to work with VAJ !
Kyle Brown
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
Your answer can be found here. This describes how to use the Sun JVM with a WebSphere client.

Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at for other WebSphere information.
Have you checked out Aspose?
subject: Can't we access EJB's deployed on WebSphere from a non IBM JVM client?
It's not a secret anymore!