Yes I also think he should implement something like this:
public class SessionListener implements HttpSessionBindingListener,
HttpSessionActivationListener, Serializable {
...
public void valueUnbound(HttpSessionBindingEvent event) {
}
...
}
and put one of those in each session t
If I do the
JkMount /application/* worker1
within my directive in httpd.conf it applies to that virtual
host only.
Alas I cannot use global JKMounts any more, but that is propably not what
you need anyways.
(tested with apache 2.0.55 and tomcat 5.0.28 on WinXP)
Hth,
Tobias
> -Original Me
Just a thought - What would happen to your application if the user
double-clicked the login button? (or whatever causes the page to load)
We also sometimes see such errors if some page loads too slow and the user
gets annoyed and logges in again (the login screen invalidates the old
session in our
Most propably you loose your session when redirecting between the protocols.
Either because you disabled cookies and do not send the
";jsessionid=aaabbbcccdddeeeff..." in your redirect, or because the cookie
is tied to the protocol. (seeing this from a security point of view, this is
the right thin
uery" parameter does and where I can find these information on
tomcat documentation.
-Nanda
-Original Message-
From: Tobias Meyer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 30, 2005 12:38 AM
To: 'Tomcat Users List'
Subject: AW: Error: Io exception: Connection reset
Maybe the user hit the "stop" button on the browser while downloading a page
or binary.
IIRC this will give you IOExceptions in your servlet when trying to push
more data in the "dead" connection.
It could also be your firewall, that times out connections which have not
been used for some time.
I
Are you using IIS as frontend on that machine?
That is where I have very similar problems...
I'll be very much interested in any findings regarding this topic.
Tobias
Edward Wynn wrote:
Hello,
I am running Tomcat 5.0.28 and am having some problems with session
invalidation / timeout that I
