This is really now an EJB question. Submit a question in regards to passivation/activation. If I was to venture I guess, here is what I think might be happening. You may be getting timeouts/exceptions in your operations on of SFSB. In the case of an exception, you have to guarantee that the remove() operation is called (in a finally block). Something tells me that this might not be getting done. As a result, those instances remain in the pool and are subject to passivation. Then, they exception you are seeing occurs.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934252#3934252 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3934252 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
