tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eriksson, Michael" <>
Subject RE: Session de-serialization problem (with patch)
Date Fri, 17 Jan 2003 15:20:10 GMT
Just a short follup:

Will you apply the patch I sent?
(Or provide an other solution with
the same effect?)

If not, please send a response so that
we can adapt correspondingly.



> -----Original Message-----
> From: Eriksson, Michael 
> Sent: Monday, December 16, 2002 12:04 PM
> To:
> Cc: Eriksson, Michael
> Subject: Session de-serialization problem (with patch)
> Hi,
> during work on session serialization my colleagues run into
> a problem with the startup order of the session manager vs
> listeners/filters.
> During startup the session manager is started before the
> listeners and filters.  This implies that objects that
> depend on parts of the application can not be properly
> deserialized. (Apparently, a re-write to remove such
> dependencies is not feasible in our case.)
> Further this behaviour is inconsistent with the reload
> behaviour, which was previously changed due to
> We have patched this behaviour (see attachment) to start
> listeners/filters immediately _befor_ the session manager.
> This patch solves our problem and does not seem to cause any
> new issues with our application.  However, due to the
> triviality of the patch, we have not made a thorough
> examination of the workings of o.a.c.core.StandardContext.
> Also, the patch is focused on one specific issue. It does
> not (unless by coincidence) ensure consistency in the
> reload/start behaviours.
> The patch is against 4.1.16, since 4.1.17 was released after
> the patch was written.
> Sincerely,
> Michael Eriksson

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message