Hi,
we've problems with stateful session beans, user transactions and passivation.
When a stateful session bean instance is part of a user transaction and JBoss
tries to passivate this bean we got the warning "Unable to passivate due to ctx lock".
This is ok, because beans cannot be passivated when they are part of a transaction.
But when I access the bean afterwards, JBoss tries to activate the bean but can't do
this because the bean wasn't passivated at all.
We got the following exception:
java.rmi.NoSuchObjectException: Could not activate; failed to restore state; Cau
sedByException is:
C:\Programme\jboss-3.2.2\server\default\tmp\sessions\MyBean-d
ruw1307-8v\druw5s8a-b5.ser (Das System kann die angegebene Datei nicht finden)
For me, this seems to be a bug in JBoss, because JBoss tries to activate a bean which
was never passivated. We're using JBoss 3.2.2.
Any comments or hints? Thanks in advance.
Helmut
<a
href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825751#3825751";>View
the original post</a>
<a
href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3825751>Reply
to the post</a>
-------------------------------------------------------
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_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
