Author: bkail Message: The WebSphere EJB container supports two stateful activation policies (ONCE and TRANSACTION), that are configured using ibm-ejb-jar-ext.xml/xml. activation-policy="ONCE" causes the SFSB to be held in memory until the bean is explicitly removed (remove() or the @Remove method). activation-policy="TRANSACTION" causes the SFSB to be passivated after completion of each transaction in which it is enlisted and activated prior to being enlisted in a transaction. There is no time-based activation policy.
You are hitting the stateful timeout, which is the duration that a stateful bean can be inactive before it is forcibly removed. It sounds like you need to increase the stateful session timeout to be at least as long as the HTTP session that contains it. To respond to this post, please click the following link: <http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14591975> ____________________________________ Unsubscribe via the "binocular" icon on the web
