lly you or others might find it useful in the future.
Yoav Shapira http://www.yoavshapira.com
>-Original Message-
>From: Steve Kirk [mailto:[EMAIL PROTECTED]
>Sent: Friday, December 10, 2004 2:19 PM
>To: 'Tomcat Users List'
>Subject: RE: sessionS info persistence
that I
wasn't aware of, so that's 2 things to fix now.
All solved now :) thanks Yoav/Ben.
> -Original Message-
> From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
> Sent: Friday 10 December 2004 14:03
> To: Tomcat Users List
> Subject: RE: sessionS info persis
On Fri, 2004-12-10 at 14:18, Steve Kirk wrote:
> You are of course right ;) I was just experiencing temporary blindness.
>
> I had overlooked an underlying grandparent class of my User class which was
> in the Session; the grandparent contains a reference to its creator, which
> is the culprit me
[EMAIL PROTECTED]
>Sent: Friday, December 10, 2004 8:25 AM
>To: 'Tomcat Users List'
>Subject: RE: sessionS info persistence when restart Tomcat
>
>
>no. I've checked this by adding more debug code to my SessionLogger
class
>(which implements all the Listener interfaces).
cats the fields together. It's parent and subclasses are all
Serializable. So is the SessionLogger itself.
> -Original Message-----
> From: Ben Souther [mailto:[EMAIL PROTECTED]
> Sent: Friday 10 December 2004 13:14
> To: Tomcat Users List
> Subject: RE
> INFO: Cannot serialize session attribute LOGGED_IN_USER
> > for session 58FD0ECF29BDCEB9DC096C5DF57A1DCC
> > java.io.NotSerializableException:
> > core.servlet.processor.SubmitLogin
> > at
> is certainly *not* the class of any object stored in the
> session - I have
Do you have a reference t
Ben Souther said:
>
> This is probably the bug you're talking about.
> http://issues.apache.org/bugzilla/show_bug.cgi?id=29521
>
>
>
Aha. Thanks Ben. That clears up most of it in one go.
So it was fixed in 5.0.29 but as far as I can see (from the Jakarta news
page and the TC download page)
ion or not.
>
> However I'd still appreciate any help that anyone can give on the other
> points below :)
>
> > -Original Message-
> > From: Steve Kirk [mailto:[EMAIL PROTECTED]
> > Sent: Friday 10 December 2004 05:50
> > To: 'Tomcat Use
gt; To: 'Tomcat Users List'
> Subject: RE: sessionS info persistence when restart Tomcat
>
>
>
> OK well after a few weeks' break from it I've returned to
> this problem with
> fresh eyes, and immediately found out something interesting.
>
> I normall
does not seem to be called.
Any help much appreciated :)
> -Original Message-
> From: Ben Souther [mailto:[EMAIL PROTECTED]
> Sent: Friday 05 November 2004 14:52
> To: Tomcat Users List
> Subject: RE: sessionS info persistence when restart Tomcat
>
>
> On Fri, 2004-11-05
On Fri, 2004-11-05 at 14:53, Mark wrote:
> The object stored in the session must implement serializable
> interface, right? Or any Java Class object can be stored in the
> session and persistence manager will take care how to save and
> restore it?
It must implement Serializable and any nested obj
The object stored in the session must implement serializable
interface, right? Or any Java Class object can be stored in the
session and persistence manager will take care how to save and
restore it?
--- Ben Souther <[EMAIL PROTECTED]> wrote:
> > aha. so it looks like it's something I screwed up
> aha. so it looks like it's something I screwed up ;)
>
I don't know. I just know that, in my case, the object that I put into
session survives restarts. The easiest way to test things like this, for
me, is to write a small test app and run it on a fresh install of
Tomcat. If it works there then
t; this case TC
> > does not serialize to SESSIONS.ser on shutdown. So I don't
> think that the
> > problem is serialisability?
> >
> > Also, still can't work out why SESSIONS.ser is only
> accessed when a new
> > warfile causes a reload
Also, still can't work out why SESSIONS.ser is only accessed when a new
> warfile causes a reload and not otherwise.
>
> > -Original Message-----
> > From: Ben Souther [mailto:[EMAIL PROTECTED]
> > Sent: Friday 05 November 2004 15:08
> > To: Tomcat Users List
> >
erwise.
> -Original Message-
> From: Ben Souther [mailto:[EMAIL PROTECTED]
> Sent: Friday 05 November 2004 15:08
> To: Tomcat Users List
> Subject: RE: sessionS info persistence when restart Tomcat
>
>
> On Fri, 2004-11-05 at 09:06, Steve Kirk wrote:
> >
On Fri, 2004-11-05 at 09:06, Steve Kirk wrote:
> > SessionDestroyed shouldn't be called when tomcat shuts down.
>
> good point. doh! but if I've understood correctly, shouldn't other methods
> of my SessionLogger be called? namely sessionWillPassivate,
> contextDestroyed (and possibly finalize
OK well to be clear yes I'm running 5.0.28 on JDK 1.4.2_05 on Win2k SP4
> -Original Message-
> From: Ben Souther [mailto:[EMAIL PROTECTED]
> Sent: Friday 05 November 2004 14:52
> To: Tomcat Users List
> Subject: RE: sessionS info persistence when restart Tomcat
>
tDestroyed not being called and was
tested under 5.0.8 and 5.5.x and working.
>
>
> >-Original Message-
> >From: Ben Souther [mailto:[EMAIL PROTECTED]
> >Sent: Thursday, November 04, 2004 9:22 PM
> >To: Tomcat Users List
> >Subject: RE: sessionS info
-
> which it does not try
> > to do when I stop TC. The log message is:
> >
> > 05-Nov-2004 00:23:26
> org.apache.catalina.session.StandardManager doUnload
> > SEVERE: IOException while saving persisted sessions:
> > java.io.FileNotFoundException:
> &g
04 9:22 PM
>To: Tomcat Users List
>Subject: RE: sessionS info persistence when restart Tomcat
>
>SessionDestroyed shouldn't be called when tomcat shuts down. Otherwise,
>the session wouldn't be valid when it starts up. I just tested with a
>clean install of 5.0.29 with
sions:
> java.io.FileNotFoundException:
> C:\jakarta-tomcat-5.0.28\work\Catalina\localhost\ao\SESSIONS.ser (The system
> cannot find the path specified)
>
> The file does not exist so the message sort of makes sense, except that this
> does not happen if I stop and then start T
ot happen if I stop and then start TC again - only if a reload is
triggered when I rebuild my warfile.
> -Original Message-
> From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
> Sent: Thursday 04 November 2004 16:09
> To: Tomcat Users List
> Subject: RE: sessionS info persistence
onths at least (and it's been around for years now) so it's
> probably in good shape.
>
> Yoav Shapira http://www.yoavshapira.com
>
>
> >-Original Message-
> >From: Mark [mailto:[EMAIL PROTECTED]
> >Sent: Thursday, November 04, 2004 2:14
>-Original Message-
>From: Mark [mailto:[EMAIL PROTECTED]
>Sent: Thursday, November 04, 2004 2:14 PM
>To: Tomcat Users List
>Subject: RE: sessionS info persistence when restart Tomcat
>
>Here some info I found:
>http://jakarta.apache.org/tomcat/tomcat-5.0-doc/co
inal Message-
> > From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
> > Sent: Thursday 04 November 2004 15:07
> > To: Tomcat Users List
> > Subject: RE: sessionS info persistence when restart Tomcat
> >
> >
> >
> > Hi,
> > Tomcat persists and
Hi,
>I had always thought all sessions were lost when the server restarts.
In
>fact I just tried it and confirmed that (5.0.28). Are we maybe talking
>about 2 different things?
I think we're talking about the same thing. Sessions are supposed to be
persisted by default.
>I have nonstandard co
files and one file called
tldCache.ser, no sessions.ser or anything that looks like a serialised
session file.
> -Original Message-
> From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
> Sent: Thursday 04 November 2004 15:07
> To: Tomcat Users List
> Subject: RE: sessionS info pers
Hi,
Tomcat persists and reloads sessions on restart by default. And the
default session timeout is 30 minutes. So you shouldn't have to do
anything.
Check out the Manager configuration reference (not the Manager webapp)
for more details and settings you can modify in this area.
Yoav Shapira ht
29 matches
Mail list logo
