Caldarale, Charles R wrote:
From: David Wall [mailto:d.w...@computer.org]
Subject: Re: TC 6.0.20 - how to know session restored on restart?
This must be a multi-thread timing issue because I had
not had this happen on several other restarts.
AFAIK, Tomcat initialization is single
work well enough for me. We already stored some info in the session
so that we could also determine the user who is associated with the
session among others, so we just created an object to hold this info
and it implements HttpSessionActivationListener and sure enough, on
tomcat restart, it
From: David Wall [mailto:d.w...@computer.org]
Subject: Re: TC 6.0.20 - how to know session restored on restart?
This must be a multi-thread timing issue because I had
not had this happen on several other restarts.
AFAIK, Tomcat initialization is single-thread.
Does this behavior make
David Wall wrote:
I am using Tomcat 6.0.20 and have implemented the SessionListener
interface. We can then use this to show a list of active sessions to
our users, and when they are logged in, we even know which user is tied
to the session. This is very handy.
I assume you mean
I am using Tomcat 6.0.20 and have implemented the SessionListener
interface. We can then use this to show a list of active sessions to
our users, and when they are logged in, we even know which user is
tied to the session. This is very handy.
However, on tomcat restart, all existing
David Wall wrote:
I am using Tomcat 6.0.20 and have implemented the SessionListener
interface. We can then use this to show a list of active sessions to
our users, and when they are logged in, we even know which user is
tied to the session. This is very handy.
However, on tomcat restart,
It seems if I can see all sessions that are started and stopped using
SessionListener, there should be no reason why we can't get the sessions
auto-built from session persistence when Tomcat restarts a web app,
too. Any tricks to figure this out?
Try reading the reply I wrote about 9
David Wall wrote:
It seems if I can see all sessions that are started and stopped using
SessionListener, there should be no reason why we can't get the sessions
auto-built from session persistence when Tomcat restarts a web app,
too. Any tricks to figure this out?
Try reading the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 8/7/2009 3:06 PM, Mark Thomas wrote:
David Wall wrote:
My first attempt was to implement those two methods in my class that
already implements HttpSessionListener, but these methods were never
called. On closer reading, it appears that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
(stupid clumsy hands prematurely hit CTRL-ENTER)
On 8/7/2009 3:38 PM, Christopher Schultz wrote:
To David: There's always JMX if you don't want to maintain the list of
sessions yourself. Look at
... the code for LambdaProbe which sniffs
My first attempt was to implement those two methods in my class that
already implements HttpSessionListener, but these methods were never
called. On closer reading, it appears that this is an interface to be
implemented by an object that I then store in the session attributes.
Do I create an
I am using Tomcat 6.0.20 and have implemented the SessionListener
interface. We can then use this to show a list of active sessions to
our users, and when they are logged in, we even know which user is tied
to the session. This is very handy.
However, on tomcat restart, all existing
12 matches
Mail list logo
