Bugs item #927062, was opened at 2004-03-31 22:05 Message generated for change (Settings changed) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=927062&group_id=22866
Category: JBossServer Group: v3.2 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Andrew Fleet (andyfleet) >Assigned to: Adrian Brock (ejort) Summary: Problem with serialization of Stateful SB handle Initial Comment: JBoss 3.2.3 JDK 1.4.1 Windows XP Hi, the main problem is described here... http://www.jboss.org/index.html?module=bb&op=viewtopic&t=47688 There are 2 issues (the main one is described above). Issue 1) JBoss appears to create a spurious Session Bean when a client serializes and deserializes the remote interface. The attached file demonstrates the issue - you'll need to tweak build.xml, but when that has been done, do ant deploy ant client The client creates a statefull session bean, invokes, stores the remote handle to a file, deserializes it and invokes on the bean (with appropriate narrowing). The second invokation goes to the correct bean, however the server output indicates the Session Bean constructor and setSessionCOntext have been called (in error). Issue 2) After having run 'ant client' I see the following output from the server (starting about 15 minutes after the 'ant client' call) 13:25:25,765 WARN [AbstractInstanceCache] Unable to passivate due to ctx lock, id=dshx0pi7-4 13:35:25,765 WARN [AbstractInstanceCache] Unable to passivate due to ctx lock, id=dshx0pi7-4 13:45:25,781 WARN [AbstractInstanceCache] Unable to passivate due to ctx lock, id=dshx0pi7-4 13:55:25,781 WARN [AbstractInstanceCache] Unable to passivate due to ctx lock, id=dshx0pi7-4 ---------------------------------------------------------------------- >Comment By: Adrian Brock (ejort) Date: 2004-04-11 16:33 Message: Logged In: YES user_id=9459 Fixed for 3.2.4 ---------------------------------------------------------------------- Comment By: Matthias Germann (germm) Date: 2004-04-09 15:36 Message: Logged In: YES user_id=740263 Hi Andrew, Issue 1: JBoss creates a new Bean instance and calls setSessuionContext each time when the method Handle.getEJBObject() is called for a stateful session bean. The call to Handle.getEJBObject() is treated as a Home interface method call. IMHO, this is wrong. Regards, Matthias ---------------------------------------------------------------------- Comment By: Matthias Germann (germm) Date: 2004-04-09 14:11 Message: Logged In: YES user_id=740263 Hi Andrew, Issue 2 is already fixed in jboss-head. getLockManager().removeLockRef(id) was not called after lock.releaseSync() in the method getEJBObject(Invocation mi) of org.jboss.ejb.StatefulSessionContainer (was fixed in Rel. 1.65). Regards, Matthias ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=927062&group_id=22866 ------------------------------------------------------- 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-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
