• Post Reply Bookmark Topic Watch Topic
  • New Topic

Stateful EJB3 was removed or timed out  RSS feed

 
Hebert Tourne
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, i have this problem in WebSphere 7 with EJB3,
I have a EJB project with one stateful ejb and one statelss ejb, and a web project with references to the two ejbs,
also i configured the WebSphere Bindings in the References of the web project.
When is when i start using the stateful ejb this exception rise:
[5/28/10 14:57:25:672 UYT] 00000017 SystemOut O 2010-05-28 14:57:25,672 ERROR [WebContainer : 2] common.contract.ejb3.SessionBeanLocalCaller - Excepcion : javax.ejb.NoSuchEJBException: Stateful bean BeanId(Regularizaciones#RegularizacionesEJB3.jar#RegularizacionesStateFulEJB, DF457FA6-0128-4000-E000-0E74C0A8EA3B) was removed or timed out.

And when this error produces, i can do any of the stateful flows, because this exception raises,
the question is, why the container not destroy this instance of the stateful, or why don't create a new one?

Thanks.
 
Hebert Tourne
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The question is:

When this error produces, i canĀ“t do any of the stateful flows, because this exception raises,
why the container do not destroy this instance of the stateful, or why don't create a new one?
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!