Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Sender: danmil
Message-ID: <3A79DF98.F4A603FF@shore.net>
Date: Thu, 01 Feb 2001 17:13:44 -0500
From: Dan Milstein <danmil@shore.net>
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org, Jim Urban <jim.urban@netsteps.net>
Subject: Re: Session Problem
References: <NEBBLJEHPAOPDJMLAICDEEEHCEAA.jim.urban@netsteps.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jim,

How are you connecting Apache to Tomcat:
 
 - Are you using the mod_jk plugin?

 - Which connector are you using (ajp13, ajp12)?

 - Are you using load balancing?

There was a bug with the load balancer in mod_jk which was causing it to
fail to read the session from the cookie if there was more than one cookie
being sent back by the web browser.  That doesn't sound like exactly what
you've been finding, but hey, who knows?  The fix for that is in the cvs
tree for 3.2 -- the file is src/native/jk/jk_lb_worker.c

Good luck,
-Dan

Jim Urban wrote:
> 
> This problem is happening on both Tomcat 3.1 and 3.2.1 on Windows NT with
> Apache.
> 
> I have a servlet based application that is having session problems.  The
> browser front end includes an applet which uses HTTP protocol to send and
> request data to and from the server.  Sometimes, not always, the servlet is
> given a new session instead of the existing session whose id was sent from
> the applet.  Here is an example of what the servlet is receiving:
> 
> HTTP METHOD:  POST
> CLIENT IP:  ***.***.***.***
> SESSION ID:  vqbuezrxy2
> SESSION ID VALID:  true
> SESSION NEW:  true
> SESSION CREATION TIME:  Wed Jan 31 11:09:32 PST 2001
> SESSION LAST ACCESS TIME:  Wed Jan 31 11:09:32 PST 2001
> SESSION ID STORED IN COOKIE:  true
> SESSION ID STORED IN URL:  false
> REQUEST HEADER:
>    content-type = [application/x-www-form-urlencoded]
>    connection = [keep-alive]
>    cookie = [JSESSIONID=buxhcnqsi1]
>    accept = [text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2]
>    host = [***.***.***.***]
>    content-length = [11]
>    user-agent = [Java1.3.0]
> 
> (I typed the *'s over the IP address for security reasons).
> 
> As you can see, the session is new and has an id of vqbuezrxy2, while the
> request header contains a cookie with a session if of buxhcnqsi1.  This
> results in our servlet failing since the new session does not contain any of
> the data the servlet needs.  We are a week away from going live and I must
> resolve this issue.  Any fix or work around will be greatly appreciated.
> 
> Please reply to jim.urban@netsteps.net

-- 

Dan Milstein // danmil@shore.net