Thanks, Hassan,
I've seen session replication mentioned and suspected that might be the
answer now.
Just stopping a worker and letting its sessions go elsewhere is certainly
more elegant than waiting around for sessions to be concluded.
The only problem is that my session data isn't serializable. So it isn't
going
anywhere in the near term.
But, again thanks. I appreciate your help. :-)
-- Scott.
Hassan Schroeder wrote:
On 2/13/07, Scott Danforth <[EMAIL PROTECTED]> wrote:
Hmmm. I just joined this mailing list today,
But, so far, nobody has responded to my posting. Maybe I'm asking about
something so trivial
or maybe you're just a wee bit impatient? :-)
I kind of expect there must be something in Tomcat like JServ's soft
shutdown
Not that it' s definitive, but I've never heard of such a thing.
Can somebody tell me what the Tomcat solution is?
Yeah, don't worry, be happy; use session replication and just pull the
plug whenever. At least that's worked for me :-)
FWIW,
--
Scott Danforth, Ph.D.
Director of Technology
ePath Learning, Inc.
70 Howard Street, Suite C
New London, CT 06320
Phone: (860) 444-6989 ext. 3
Fax: (215) 243-7454
email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
