Win a copy of Machine Learning with R: Expert techniques for predictive modeling this week in the Artificial Intelligence and Machine Learning 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Junilu Lacar
  • Jeanne Boyarsky
  • Bear Bibeault
  • Knute Snortum
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • Frits Walraven
  • Ganesh Patekar

Misterious problem calling remote EJB3 on Websphere 7

Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, i have two ears deployed in the same server, Websphere 7. One EAR contain my EJBs3 and the other EAR contain a web application, and i want to try to call remote EJBs through annontation and JNDI lookup.

In the web application EAR, i have the following Servlet:

And, in the EAR containing EJBs i have the following Session Stateless bean and his remote interface:

Ok, if i deploy the two ears in the server and execute the servlet, it works well, i get the EJBs by the two ways (annontation and JNDI lookup), and i get the expected trace (a simple text in the console):

But now, if i restart the EAR containing de web application, it doesn't work fine, i get the EJB annotated but i can't get the EJB through JNDI lookup and get the following trace:

What's wrong?, any idea?

Thanks in advanced!
Stinging nettles are edible. But I really want to see you try to eat this tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!