Hi all,
Please suggest a solution for following problem.
Problem - Standalone JAVA client unable to access clustered EJBs hosted on WAS 5.x
Description - Standalone JAVA client is unable to lookup EJB hosted in a clustered environment in WAS 5.x. The initial context lookup works in few of the cases below but the EJB lookup using the JNDI name doesn't work for any of them. I tried following combinations -
1. IBM JDK 1.3 and use of WAS specific jar files (e.g. naming.jar, namingclient.jar etc.) on client side.
2. IBM JDK 1.3 and use of WAS Pluggable client to create environment for Standalone JAVA client
3. SUN JDK 1.4.x and use of SUN context factory with no WAS specific jar files on client side
4. SUN JDK 1.4.x and use of WAS context factory with WAS specific jar files on client side
5. SUN JDK 1.4.x and use of WAS Pluggable client to create environment for Standalone JAVA client
6. SUN JDK 1.3.x and use of WAS Pluggable client to create environment for Standalone JAVA client
None of the above combinations worked.
To add a few points:
1. SUN JDK 1.4.x throws outofmemory exception when none of WAS jar files are used on client side.
2. In few of the cases i got ORB 1.3x incompatible with JDK 1.4.x version error.
3. Format of provider URL that i tried -
corbaloc:::
corbaloc:iiop::
iiop://:
4. JNDI for EJB that I tried -
cell/clusters//
java:comp/env/
java:comp/env/cell/clusters//
The ultimate aim of this standalone java client accessing clustered EJB on WAS is to find out if the remote clustered EJB hosted on WAS will work with a JBOSS client. If someone knows any different way to do a JNDI lookup for clustered EJBs hosted on WAS from a JBOSS client then please post the solution here. And if this is not possible then please provide an official reference link from either IBM or JBOSS website.
Thank you all,
With regards,
Bharat.
