• 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 ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Bear Bibeault
  • Rob Spoor
  • Henry Wong
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Frits Walraven
  • Himai Minh
  • Jj Roberts

javax.naming.NameNotFound Exception

Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Friends

I tried several options to run my client Program but failed.
I have deployed my addressbook.ear in to Orion Server.
below is the Deployment Descriptor ejb-jar.xml configured with ejbname, Home ,Remote and Ejb Bean


and the application-client.xml is configured as


and in my client program i am trying to get the HomeRefence as

Context initial = getInitialContext();
Object homeref = initial.lookup("java:comp/env/ejb/AddressEntry");
AddressBook home = (AddressBook)PortableRemoteObject.narrow(homeref,AddressBook.class);


and getInitialContext() is set as

ctx = new InitialContext(ht);
return ctx;

Each time i am getting the same message by running my Client as:

MESSAGE:java:comp/env/ejb/AddressEntry not found in <global>
at com.evermind.server.rmi.RMIContext.lookup(.:121)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at addressbook.ejb.SessionClient.main(Unknown Source)

can any body give a lead to find where i am going wrong

[ December 15, 2004: Message edited by: Phani M ]
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
With every appserver I have worked with there has to be a vendor-specific descriptor accompanying the ejb-jar.xml. In JBoss this file is jboss.xml, and I guess that there must be one for Orion too.
In this file you have to map the ejb names to the JNDI names. Here is an example from jboss.xml.

The thing to remember here is that the ejb-name tag in ejb-jar.xml is NOT the JNDI name. Maybe this is the solution to your problem.
It's hard to fight evil. The little things, like a nice sandwich, really helps. Right tiny ad?
SKIP - a book about connecting industrious people with elderly land owners
    Bookmark Topic Watch Topic
  • New Topic