• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

NameNotFoundException WAS5.1

 
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Lost a day trying to install an EAR file with 3 EJB and 1 WAR...
I'm working with WAS5.1, WSAD5.1.1, SQLServer2000, Windows2003.
My configuration uses:
- the file EAR/META-INF/Application.xml riferences to the 3 Ejb Jar and to WebModule
- the file EAR/META-INF/Manifest.mf references to the 3 EJB Jar
- the file WAR/META-INF/Manifest.mf references to the 3 EJB Jar
- the files *.xmi should be correct
Most of these files have been used to deploy EAR file in JBoss so EJB/JNDI names are not mystiped.
I understand I am missing something and wanted to find a solution before buying a great book.
I have this exception:
getEJBref(cse.topselectormanager.TopSelectorManagerHome):
Couldn't get a JNDI object reference!: javax.naming.NameNotFoundException:
Context: BPV01Network/nodes/BPV01/servers/nodeagent,
name: cse.topselectormanager.TopSelectorManagerHome:
First component in name cse.topselectormanager.TopSelectorManagerHome not found.
Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0
More, if I use dumpNameSpace.bat what output should I see?
A list of EJB Jndi Names?
Any tips?
Thks in advance
Leonardo
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, you should see a list of JNDI names. And my guess is that cse.topselectormanager.TopSelectorManagerHome will not be among them. For instance, in WebSphere, the standard is to use something like cse/topselectormanager/TopSelectorManagerHome. So, are you SURE you didn't configure the names in that way? Could you post the contents of ejb-jar-bnd.xmi?
Kyle
 
leonardo battagli
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Kyle,
Solution is much simpler.
I was using a network of cells with 1 Network Deployment Manager and 2 Application Servers (All of them are in the same machine).
In this configuration there are 3 different name server, the first is on port 2809 (Network Deployment Manager Name Server) and the other two are on 9810 and 9811.
So the problem was because I was using port 2809 instead of 9810 !!!
After having fixed that everything went ok!!
Do you agree with this?
WAS5 has 1 Name Server for each Application Server so I got in error
thks
Leonardo

Originally posted by Kyle Brown:
Yes, you should see a list of JNDI names. And my guess is that cse.topselectormanager.TopSelectorManagerHome will not be among them. For instance, in WebSphere, the standard is to use something like cse/topselectormanager/TopSelectorManagerHome. So, are you SURE you didn't configure the names in that way? Could you post the contents of ejb-jar-bnd.xmi?
Kyle

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I faced the same issue and changing the port worked for me !

Thanks !!!
 
reply
    Bookmark Topic Watch Topic
  • New Topic