This change, serializing local proxies as well as remote ones, breaks the local ejb-link naming tests on my machine: previously only the remote ones were broken.
In the nightly tests, the remote tests (not the local) also failed on jdk 1.4, a similar setup to mine. http://www.lubega.com/testarchive/sun_j2sdk140/org/jboss/test/naming/test/InternalNamingClassReplacementUnitTestCase.html As far as I can tell, the serialization code is keeping the first version of the class it sees, forever. I haven't dug into sun's code yet, however. (Is it available for 1.4 anyway?) I would think this change to serialized storage of local proxies would slow things down significantly compared to references. I was considering changing storage of remote proxies to references as well, on the argument that local access is expected to be more frequent than remote access, so the cost of serializing a referenced proxy for each remote call would be less than the cost of deserializing a serialized proxy for a local call. It would also fix these tests on more systems. Any comments? thanks david jencks On 2002.04.18 12:58:29 -0400 [EMAIL PROTECTED] wrote: > Bugs item #541855, was opened at 2002-04-09 22: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: Closed > >Resolution: Fixed > Priority: 6 > Submitted By: Stephen Coy (scoy) > Assigned to: Scott M Stark (starksm) > 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: Scott M Stark (starksm) > Date: 2002-04-18 09:58 > > Message: > Logged In: YES > user_id=175228 > > Fixed on head and the 3.0 branch > > ---------------------------------------------------------------------- > > Comment By: Stephen Coy (scoy) > Date: 2002-04-17 01: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 00: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 > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
