File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes BEA/Weblogic and the fly likes Unable to resolve jndi name Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Unable to resolve jndi name" Watch "Unable to resolve jndi name" New topic

Unable to resolve jndi name

Priya Venkatesan
Ranch Hand

Joined: Nov 02, 2002
Posts: 61
I have set the jndi-name as "ejb20-basic-containerManaged-CabinHome" in my weblogic-ejb-jar.xml file. I built all the required container classes using ant. While running the client, Iam getting the follo. error:
The client was unable to lookup the EJBHome. Please make sure that you have dep
loyed the ejb with the JNDI name ejb20-containerManaged-CabinHome on the WebLogi
c server at t3://localhost:7001
Unable to look up the beans home: Unable to resolve 'ejb20-containerManaged-Cabi
nHome' Resolved: '' Unresolved:'ejb20-containerManaged-CabinHome'
Can someone tell me what needs to be done
Valery Anciaux
Ranch Hand

Joined: May 14, 2001
Posts: 45
Reset your jndi name without the 'basic' word...
Basic, isn't it ?
Priya Venkatesan
Ranch Hand

Joined: Nov 02, 2002
Posts: 61
Sorry, I think I mentioned it wrong. I have put "ejb20-containerManaged-CabinHome" in my weblogic-ejb-jar.xml.
Not sure why this is coming up. Any other suggestions.
Sai Prasad
Ranch Hand

Joined: Feb 25, 2002
Posts: 560
Try some simple names. Also you can view the JNDI tree by selecting the context menu when you right click on the server link in weblogic administration console. You should see your JNDI name there. Also there could be a problem in your xml or bean files. Try to use the console to undeploy and redeploy the bean. You may see some exceptions.
Priya Venkatesan
Ranch Hand

Joined: Nov 02, 2002
Posts: 61
ThankYou Sai. I fixed the error. Seems like my beans were not deployed properly. Thanks again for pointing me in the right direction.
I agree. Here's the link:
subject: Unable to resolve jndi name
It's not a secret anymore!