Author: gas Message: Hi,
These are two different things. Bean state is passivated when it is not in transaction, based on activation policy (see bkail response in your other post). Timeout is used by the container to detect 'abandoned' beans that should be removed. You are hitting that one. Your bean is inactive longer than 10 minutes, so removed. Unfortunately you can not change it in the FEP EJB 3.0, see limitations on this page: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.ejbfep.multiplatform.doc/info/ae/ae/rejb_limitationsejbfp.html If you need longer timeout you can: - migrate to WAS v7, where this setting is supported - http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.express.doc/info/exp/ae/cejb_bindingsejbfp.html - switch to use EJB 2.1, where you can override it per bean - introduce a heartbeat in the app, that will call bean once a few minutes. It is very strange that you are hitting this timeout, as it means that client has not called the bean for very long time. SFSBs usually act as Facade to the application, so they should be limited in number and called quite often. To respond to this post, please click the following link: <http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14592117> ____________________________________ Unsubscribe via the "binocular" icon on the web
