On Wed, 30 May 2001, Remy Maucherat wrote:
> > On Wed, 30 May 2001, Remy Maucherat wrote:
> >
> > > CL was indeed broken when stopping the manager.
> > > I have committed something which should fix it.
> > >
> > > [Note : My build environment is totally messed up, so I wasn't able to
> test
> > > with Watchdog or the tester]
> > >
> >
> > Downloading as I type. I'll let you know if I see anything.
> >
Tester and Watchdog pass, by the way.
> > Jon, could you give me one of your patented "cookbooks" for recreating
> > this just in case? My current unit tests do deserialization on reload,
> > and the classes are loaded from a JAR file in WEB-INF/lib, so there must
> > also be something else different about what Scarab is doing.
>
> Really ?
> Perhaps my fix wouldn't fix anything then ... The trace Jon posted was
> really clear about where the problem was, though :
>
> ...
> org.apache.catalina.session.StandardSession.writeObjectData(StandardS
> ession.java:707)
> at
> org.apache.catalina.session.StandardManager.unload(StandardManager.ja
> va:502)
> at
> org.apache.catalina.session.StandardManager.stop(StandardManager.java
> :648)
> at
> org.apache.catalina.core.StandardContext.reload(StandardContext.java:
> 2316)
> ...
>
> The catalina internal thread was indeed unbound before calling reload (so
> that's why the manager failed to load the class when trying to serialize).
>
My interest is in why this problem didn't affect the tester tests, which
go through what *sounds* like exactly the same process, yet it has not
failed to correctly reload session attributes after a restart. Clearly
the tests don't cover the failure mode that Jon encountered, so I want to
be able to explore the differences.
> Remy
>
>
Craig
