Bug #240 (closed)
Opened 18 years ago
Closed 16 years ago
RenderingEngine exceptions may kill the RenderingBean
Reported by: | jamoore | Owned by: | cxallan |
---|---|---|---|
Priority: | minor | Cc: | jburel |
Sprint: | n.a. | ||
Total Remaining Time: | n.a. |
Description
We had a case recently where the RenderingBean was being destroyed for no "apparent" reason (meaning the client didn't get an exception). Rather on subsequent use of the handle the following was thrown:
javax.ejb.EJBNoSuchObjectException: Could not find Stateful bean: a1o6e-6b235h-eps2fqgx-1-epscfou8-f at org.jboss.ejb3.cache.simple.SimpleStatefulCache.get(SimpleStatefulCache.java:266) at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:59) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:167) at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:100) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) ...etc...
The exceptions which can be thrown by the RE should be reviewd, as well as the catching strategy.
Change History (4)
comment:1 Changed 18 years ago by jmoore
- Milestone changed from Unscheduled to 3.0-M4
comment:2 Changed 17 years ago by jmoore
- Milestone changed from 3.0-Beta2 to 3.0-Beta3
comment:4 Changed 16 years ago by cxallan
- Resolution set to fixed
- Status changed from new to closed
- Version 3.0-M3 deleted
This appears to be resolved with OmeroSessions. We can re-open as necessary.
Most likely fixed, but rescheduling with #334.