Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.218.213 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=F1AvDAJPhAEJCWJxaPU20BKQWC7fZBYyU6+RFhlIBqSUsnSo/s9ag4Ss1NHUmBWv5R
         R7YdSpAmfjTHgk9HXOgoaVKNiBrjqmuk43GBnZ3dyKN+dhPKlaOdHjo0kJGC3WW+vWsw
         hQ2Ky0mYKkn/pym8F6hfcaEUCcpGvTq2Vyu1o=
MIME-Version: 1.0
In-Reply-To: <t2s84347691004201547p4b7b3336l61a9b8313c6105b2@mail.gmail.com>
References: <t2s84347691004201547p4b7b3336l61a9b8313c6105b2@mail.gmail.com>
Date: Wed, 21 Apr 2010 03:46:11 +0400
Message-ID: <n2j427155181004201646ldc157522ucbed7fd117d12ee4@mail.gmail.com>
Subject: Re: JSESSIONID being lost
From: Konstantin Kolinko <knst.kolinko@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2010/4/21 Jim Goodspeed <goodspeedster@gmail.com>:
> Our current setup is two hardware load balancers (layer 4) in front of tw=
o
> Apache servers (2.2.14) which sit in front of two tomcat servers (6.0.20)=
.
> The hardware load balancers load balance apache and apache load balances
> tomcat using AJP via mod_proxy. =A0Apache and Tomcat are running on RHEL4
> 32-bit. =A0The JVM is 1.6.
>

1. Note that there can be
https://issues.apache.org/bugzilla/show_bug.cgi?id=3D48345
"Session does time-out shorter than setting in web.xml when
PersistentManager is used. "

2. Maybe implementing a javax.servlet.http.HttpSessionListener will
allow you to catch the circumstances when your issue happens.  Note,
that if you add it to ${catalina.base}/conf/web.xml, it will be
present in all the web applications deployed on your server.

That is, if the session actually expires on the server.

> We have a situation where the JSESSIONID seems to get lost
> somewhere in a users transaction - the result is they get kicked back to =
the
> applications login page (no sessionid so the app thinks they haven't logg=
ed
> in).

Do you have any evidences on what actually happens? E.g., you can
iterate over request headers to see if the cookie is actually present,
and what path it contains, etc.


Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org