Bugs item #541855, was opened at 2002-04-10 15:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=541855&group_id=22866
Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 6 Submitted By: Stephen Coy (scoy) Assigned to: Nobody/Anonymous (nobody) Summary: Passivation of stateful sess beans fails Initial Comment: Section 7.4.1 of the EJB2.0 spec says that EJBLocalHome and EJBLocalObject (amongst others) should be persisted during passivation. The code in org.jboss.ejb.plugins.SessionObjectOutputStream clearly doesn't do this yet. Someone needs to check and ifx this code for EJB2.0 conformance. ---------------------------------------------------------------------- >Comment By: Stephen Coy (scoy) Date: 2002-04-17 18:10 Message: Logged In: YES user_id=463096 Doh! I figured out that I can set the cache size to 1. Creating a second session bean causes the first to be passivated. We now have a test that successfully fails. ---------------------------------------------------------------------- Comment By: Stephen Coy (scoy) Date: 2002-04-17 17:17 Message: Logged In: YES user_id=463096 The attached files incorporate test case "stateful2" into the JBoss test suite. Please remove any .DS_Store files you find - they're an unfortunate side effect of using MacOS at present. I spent quite some time trrying to configure the container so that the session bean would passivate before the test completed, but failed miserably. However, you can still see the passivation failing when the EJB is undeployed. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=541855&group_id=22866 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
