stateful session beans will timout after a set time, causing the error you see. You can either edit standardjboss.xml, the stateful session bean section (increase timeouts), or maybe better (?) copy paste config to your jboss.xml and then edit so you can make changes for this app only
Could your SSB have a one hour time out set ?
Thank you very much for your responses. I am looking over my standardjboss.xml file. Here's what I have within the Standard Stateful SessionBean "container-configuration".
Shouldn't I expect my stateful session beans to be passivated after 600 sec (10 min) of inactivity? If this is true, wouldn't I expect to see a ***.ser file appear in the $JBOSS_HOME/server/default/db/sessions/[SessionBeanName]/ directory? This isn't happening.
I've seen some other topic postings related to Stateful Sessions beans not being passivated.
Could this be a JBoss bug?
I have been able to repeat this problem with JBoss/Tomcat and on a Windows machine.
I tried deploying to the EJB 2.0 standard with no improvement.
I am really stumped and frustrated with this one. Why is JBoss trying to activate Session beans that have not been passivated? It would appear this is the case.
Is anyone else experiencing this problem?
you are probably in the wrong forum to get a decent answer to this - this is probably not specifically a web problem