: 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 normally run TC (5.0.28) as a windows service. So upon
re-reading this
thread, Yoav's earlier comment
]
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). Every time a session
event
is fired, my listener
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 persistence when restart Tomcat
Hi
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 when restart Tomcat
You are of course right
Hi Steve,
I am jumping into this discussion rather late and I am probably not going to
answer any of your questions. I just would like to add that I examined the
session persistence and listeners topic also very deep some weeks ago. After
all I found it not really practical because the servlet
points below :)
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Friday 10 December 2004 05:50
To: 'Tomcat Users List'
Subject: RE: sessionS info persistence when restart Tomcat
OK well after a few weeks' break from it I've returned
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) there
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 to it in
Souther [mailto:[EMAIL PROTECTED]
Sent: Friday 10 December 2004 13:14
To: Tomcat Users List
Subject: RE: sessionS info persistence when restart Tomcat
INFO: Cannot serialize session attribute LOGGED_IN_USER
for session 58FD0ECF29BDCEB9DC096C5DF57A1DCC
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
:)
-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 at 08:29, Shapira, Yoav wrote:
Hi,
Are you running Tomcat as a windows service? If so
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 a similar listener to the one you
describe
To: Tomcat Users List
Subject: RE: sessionS info persistence when restart Tomcat
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
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 persistence when restart Tomcat
SessionDestroyed shouldn't be called
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
On Fri, 2004-11-05 at 08
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
-
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:
SessionDestroyed shouldn't be called when tomcat shuts down.
good point
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:
SessionDestroyed shouldn't be called when tomcat shuts down.
good point. doh
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
Subject: RE: sessionS info persistence when restart Tomcat
On Fri
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 I
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 ;)
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
Hi,
Is it possible to save sessions info, so when Tomcat restarts all
previously active sessions will be loaded.
I'm trying to prevent user's re-login when Tomcat goes down for short
period (5-15 minutes) of time.
Thanks,
Mark
__
Do you
http://www.yoavshapira.com
-Original Message-
From: Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 04, 2004 10:04 AM
To: [EMAIL PROTECTED]
Subject: sessionS info persistence when restart Tomcat
Hi,
Is it possible to save sessions info, so when Tomcat restarts all
previously
.
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 04, 2004 10:04 AM
To: [EMAIL PROTECTED]
Subject: sessionS info persistence when restart Tomcat
Hi,
Is it possible to save sessions info, so when Tomcat
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
: RE: sessionS info persistence when restart Tomcat
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
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/config/manager.html
but...:
--cut -
Persistent
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 PM
To: Tomcat Users List
Subject: RE: sessionS info persistence when restart Tomcat
Here some info I found:
http
2004 16:09
To: Tomcat Users List
Subject: RE: sessionS info persistence when restart Tomcat
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
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 when restart Tomcat
Hi,
I
31 matches
Mail list logo
