EJB 3.0: java.io.IOException: Unable to find session object ...

Question

Hello,
We have an EJB3 application deployed to an Oracle AS 10.1.3.1.0 instance.
Our main point of entry to the application is a stateful session bean (that controls access), that has injected several other stateful session beans.
Like this:
+@Stateful(name = "TstreamUserSession")+
+public class TstreamUserSessionBean extends UserSessionBean implements TstreamUserSession {+
+@EJB(name = "ContactSession")+
private ContactSessionLocal contactSession;
+@EJB(name = "GuestSession")+
private GuestSessionLocal guestSession;
+@EJB(name = "TechCustomerSession")+
private TechCustomerSessionLocal techCustomerSession;
+@EJB(name = "PmSession")+
private PmSessionLocal pmSession;
+@EJB(name = "CustomerSession")+
private CustomerSessionLocal customerSession;
+@EJB(name = "PartnerSession")+
private PartnerSessionLocal partnerSession;
+@EJB(name = "AdminSession")+
private AdminSessionLocal adminSession;
+@EJB(name = "SuperAdminSession")+
private SuperAdminSessionLocal superAdminSession;
+@EJB(name = "VmSession")+
private VmSessionLocal vmSession;
+public TstreamUserSessionBean() {+
+}+
+...+
In this class, we also look up these sessions, because we need several instances of these, in this manner:
+private synchronized Object getSessionInstance(String sessionName) throws AccessDeniedException {+
          +try {+
               InitialContext ic = new InitialContext();
               return ic.lookup("java:comp/env/" sessionName);+
          +} catch (NamingException e) {+
          +}+
     +}+
However, we keep getting the following messages after a certain period.
java.io.IOException: Unable to find session object 2816103596632839360 for location 'AdminSession'
+10/01/12 11:50:04 at com.evermind.server.ejb.EJBInternalInputStream.resolveObject(EJBInternalInputStream.java:70)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.checkResolve(ObjectInputStream.java:1346)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.activateBean(StatefulSessionEJBObject.java:581)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.remove_X(StatefulSessionEJBObject.java:213)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.remove_X(StatefulSessionEJBObject.java:159)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBHome.processTimedOutSessions(StatefulSessionEJBHome.java:371)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBHome.cleanUpMaintenance(StatefulSessionEJBHome.java:306)+
+10/01/12 11:50:04 at com.evermind.server.ejb.EJBTask.run(EJBTask.java:47)+
+10/01/12 11:50:04 at com.evermind.util.Task.schedule(Task.java:51)+
+10/01/12 11:50:04 at com.evermind.util.TaskManager.run(TaskManager.java:221)+
+10/01/12 11:50:04 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)+
+10/01/12 11:50:04 at java.lang.Thread.run(Thread.java:595)+
I guess this occurs when the stateful session TstreamUserSession is reactivated?
Or when the ones being injected are passivated?
Any idea why this occurs, or how to suppress it, because it really spams our logs...
Thanks.

Answer 1

Hello,
We have an EJB3 application deployed to an Oracle AS 10.1.3.1.0 instance.
Our main point of entry to the application is a stateful session bean (that controls access), that has injected several other stateful session beans.
Like this:
+@Stateful(name = "TstreamUserSession")+
+public class TstreamUserSessionBean extends UserSessionBean implements TstreamUserSession {+
+@EJB(name = "ContactSession")+
private ContactSessionLocal contactSession;
+@EJB(name = "GuestSession")+
private GuestSessionLocal guestSession;
+@EJB(name = "TechCustomerSession")+
private TechCustomerSessionLocal techCustomerSession;
+@EJB(name = "PmSession")+
private PmSessionLocal pmSession;
+@EJB(name = "CustomerSession")+
private CustomerSessionLocal customerSession;
+@EJB(name = "PartnerSession")+
private PartnerSessionLocal partnerSession;
+@EJB(name = "AdminSession")+
private AdminSessionLocal adminSession;
+@EJB(name = "SuperAdminSession")+
private SuperAdminSessionLocal superAdminSession;
+@EJB(name = "VmSession")+
private VmSessionLocal vmSession;
+public TstreamUserSessionBean() {+
+}+
+...+
In this class, we also look up these sessions, because we need several instances of these, in this manner:
+private synchronized Object getSessionInstance(String sessionName) throws AccessDeniedException {+
          +try {+
               InitialContext ic = new InitialContext();
               return ic.lookup("java:comp/env/" sessionName);+
          +} catch (NamingException e) {+
          +}+
     +}+
However, we keep getting the following messages after a certain period.
java.io.IOException: Unable to find session object 2816103596632839360 for location 'AdminSession'
+10/01/12 11:50:04 at com.evermind.server.ejb.EJBInternalInputStream.resolveObject(EJBInternalInputStream.java:70)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.checkResolve(ObjectInputStream.java:1346)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.activateBean(StatefulSessionEJBObject.java:581)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.remove_X(StatefulSessionEJBObject.java:213)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.remove_X(StatefulSessionEJBObject.java:159)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBHome.processTimedOutSessions(StatefulSessionEJBHome.java:371)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBHome.cleanUpMaintenance(StatefulSessionEJBHome.java:306)+
+10/01/12 11:50:04 at com.evermind.server.ejb.EJBTask.run(EJBTask.java:47)+
+10/01/12 11:50:04 at com.evermind.util.Task.schedule(Task.java:51)+
+10/01/12 11:50:04 at com.evermind.util.TaskManager.run(TaskManager.java:221)+
+10/01/12 11:50:04 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)+
+10/01/12 11:50:04 at java.lang.Thread.run(Thread.java:595)+
I guess this occurs when the stateful session TstreamUserSession is reactivated?
Or when the ones being injected are passivated?
Any idea why this occurs, or how to suppress it, because it really spams our logs...
Thanks.