From the bea-weblogic site: For passivated EJB instances: After a stateful session EJB instance has been passivated, a client must use the EJB instance before idle-timeout-seconds is reached. Otherwise, WebLogic Server removes the passivated instance from disk. but as per the definition the idel-timeout-seconds : idle-timeout-seconds defines the maximum length of time a stateful EJB should remain in the cache. After this time has elapsed, WebLogic Server may remove the bean instance if the number of beans in cache approaches the limit of max-beans-in-cache. so as per the definition the first para sounds different? can some one explain?? thanks, trupti
First off, you will get a better response in the future if you post WebLogic questions to the WebLogic Forum. Onto the answer: Your confusion over this topic springs from the fact that idle-timeout-seconds is used for both Entity Beans and Stateful Session Beans yet holds slightly different meanings for each. In the case of Entity Beans, idle-timeout-seconds represents the length of time an Entity should remain in the cache before it is available for removal. In the case of Stateful Session Beans, idle-timeout-seconds represents the length of time the session will be available before it is removed. You can understand this as: When idle-timeout-seconds has been reached then the Container will remove this session. Therefore, both descriptions you found are correct, you just need to understand what component is being referred to. It was possibly a bad idea for BEA to reuse the same element name for both Entity Beans and Stateful Session Beans since the functionality is slightly different.
Actually it is very confusing because the only mention about idle-timeout-seconds to consider entity beans, is in the DTD of bea ejb.pdf In chap 4, the explanation only states stateful session beans with respect to the cache and idle timout.
Quite confusing! faiza
Who among you feels worthy enough to be my best friend? Test 1 is to read this tiny ad: