The TransactionRolledbackException above is caused by the following situtation we have: At the client there are lookup to two stateful session beans... bean1 and bean2. When the client exits it calls ejbRemove for bean1 and bean2. By the way... bean1 and bean2 are passivated in this situation. bean1 can be removed without any problem, but when removing bean2 it looks like bean2 has already been removed by the server or the application server tries to activate bean2 but bean2 has already been removed. This perhaps could be a bug: why should the server try to activate the session if it no longer exists.
I solved this special problem by removing bean2 before bean1 but I don't know why. I have not solved the problem for "Unable to passivate due to ctx lock". It would be nice to get information about active transactions that are not closed. JÃrgen View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828286#3828286 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3828286 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
