Ok, I will try to explain it one more time. Hope it is clearer. The issue is when both are set to 3600 (secs). Users expect to see the bean goes away in one hour. If, however, the pool size is set to 2, after creating the 3rd bean, bean #1 will be passivated. Next when the remover thread comes in to check for ageout items to remove, bean #1 will be removed immediately (instead of 3600 seconds later). This is because the remove thread determine when to remove the passivated bean based on the delta of (max-bean-life and max-bean-age).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918604#3918604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3918604 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
