Win a copy of Node.js Design Patterns: Design and implement production-grade Node.js applications using proven patterns and techniques this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

JNDI lookup of a clustered EJB hosted on WAS from standalone/JBOSS client

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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::<hostname>:<port>
corbaloc:iiop:<hostname>:<port>
iiop://<hostname>:<port>;
4. JNDI for EJB that I tried -
cell/clusters/<clustername>/<EJBname>
java:comp/env/<EJBname>
java:comp/env/cell/clusters/<clustername>/<EJBname>

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.
 
Sheriff
Posts: 67592
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"bharatparikh bharatparikh",

There aren't many rules that you need to worry about here on the Ranch, but one that we take very seriously regards the use of proper names. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it.

In particular, your display name must be a first and a last name separated by a space character, and must not be obviously fictitious.

Thanks!
bear
JavaRanch Sheriff
 
Bharat Parikh
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sorry for that. Updated the display name. Thanks.

With regards,
Bharat.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic