Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
The moose likes Websphere and the fly likes Remote EJB3.0 access from Spring Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Remote EJB3.0 access from Spring" Watch "Remote EJB3.0 access from Spring" New topic

Remote EJB3.0 access from Spring

Nitin Gaur

Joined: Sep 06, 2003
Posts: 27
I have 2 applications - one EAR containing EJB3.0 and other its Spring client. Both deployed on same Websphere app server 7 instance i.e. same JVM.

Here are couple of client parts:


Client code snippet:

This works fine. EJB access deployed in other application in same container, works.

But it does not work if I move that client to other machine in same network and just change provider URL and give remote server IP instead of localhost. JNDI lookup problem occurs

Exact Error: Error 500: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ruleService' defined in class path resource [applicationContext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: Context: CFSDDVM2399Node01Cell/nodes/CFSDDVM2399Node01/servers/server1, name: com.ecrd.ruleservice.Customer_Management_Service_JavaBusiness: First component in name com.ecrd.ruleservice.Customer_Management_Service_JavaBusiness not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound:]

I can't figure out what changes (and where) are required to connect to EJB hosted in different server JVM. Any help or suggestion are welcome.

If you don't like something, change it. If you can't change it, change your attitude. Don't complain.
Mark Spritzler

Joined: Feb 05, 2001
Posts: 17276

You will have to look at the WebSphere docs to figure out the jndi properties that need to be set for accessing the JNDI Tree in Websphere. So this is a WebSphere question. Meaning if you weren't using Spring, you would still have this issue.

I am going to move this to WebSphere and let them help you because they are the experts on WebSphere.

Good Luck


Perfect World Programming, LLC - iOS Apps
How to Ask Questions the Smart Way FAQ
Nitin Gaur

Joined: Sep 06, 2003
Posts: 27
Error is resolved. I work on virtual machine. All developer images were copied from a particular VM and that brought over WAS configs (hostname, cell, node etc) with it. Remote access worked after fixing all occurances of hostnames in serverindex.xml of the server hosting EJB.
I agree. Here's the link:
subject: Remote EJB3.0 access from Spring
It's not a secret anymore!