You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Krishna Ganti <km...@yahoo.com> on 2003/11/04 22:58:15 UTC
Session mixup problem in Tomcat with Coyote Connector
Hi,
We are seeing a session mixup problem in a deployed
tomcat instance running with coyote connector. A user
is seeing another user's data and request parameters.
We took a look at the Coyote code and found out that
parameters are not reset till the next request. If a
thread switch were to occur during this time (due to
an exception), is it possible for session data to get
mixed up? Please let us know how we can further
investigate the problem or if you have a solution for
this.
Someone please help ASAP because this is a production
issue we are facing.
Thanks,
Krishna.
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
AW: Session mixup problem in Tomcat with Coyote Connector
Posted by Markus Heussen <he...@rheinland-online.com>.
We have the same problem in our production enviroment. We also need help to
solve it.
* Win2K
* first Apache Tomcat/4.1.18 with JDK 1.3.1_07-b02
* Apache 2.0.44 in Front of the Tomcat an with mod_jk2 2.0.43 running for
load balancing
* JBoss 3.2.1 with a separate JDK 1.3.1_07 included a Tomcat 4.1.24
Sometimes it happens that one user gets sessions attributes stored in
another users context.
Thanks to anyone who can help.
Markus
-----Ursprungliche Nachricht-----
Von: Krishna Ganti
Gesendet: Dienstag, 4. November 2003 22:58
An: tomcat-user@jakarta.apache.org
Betreff: Session mixup problem in Tomcat with Coyote Connector
Hi,
We are seeing a session mixup problem in a deployed
tomcat instance running with coyote connector. A user
is seeing another user's data and request parameters.
We took a look at the Coyote code and found out that
parameters are not reset till the next request. If a
thread switch were to occur during this time (due to
an exception), is it possible for session data to get
mixed up? Please let us know how we can further
investigate the problem or if you have a solution for
this.
Someone please help ASAP because this is a production
issue we are facing.
Thanks,
Krishna.
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RE: Session mixup problem in Tomcat with Coyote Connector
Posted by Tracy Saward <tr...@fleetward.com>.
Hi,
We are independent consultants currently undertaking a study of satisfaction
among end-users of Open Source Software, notably Tomcat, for a company which
has asked us for recommendations in terms of deploying policy for such
systems.
I was hoping to set up a quick (5 minute) telephone interview with yourself
or the appropriate person to discuss your experience with this product to
date.
Please feel free to telephone me anytime, or reply to this e-mail indicating
an appropriate time/person for me to recall.
Thanks for your gracious attention to this request!
Best regards,
Tracy
Tracy Saward
Fleetward Group
85 Maskell Street
St Heliers
Auckland
New Zealand
Tel: 64 9 575 1626
Fax: 64 9 585 0939
Mail: tracys@fleetward.com
-----Original Message-----
From: Krishna Ganti [mailto:kmganti_tomcat@yahoo.com]
Sent: Wednesday, November 05, 2003 10:58 AM
To: tomcat-user@jakarta.apache.org
Subject: Session mixup problem in Tomcat with Coyote Connector
Hi,
We are seeing a session mixup problem in a deployed
tomcat instance running with coyote connector. A user
is seeing another user's data and request parameters.
We took a look at the Coyote code and found out that
parameters are not reset till the next request. If a
thread switch were to occur during this time (due to
an exception), is it possible for session data to get
mixed up? Please let us know how we can further
investigate the problem or if you have a solution for
this.
Someone please help ASAP because this is a production
issue we are facing.
Thanks,
Krishna.
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org