You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Sandy McArthur <Sa...@McArthur.org> on 2004/07/16 00:01:01 UTC
Re: mod_jk 1.2.6 release ? - session tracking cookie
On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote:
> Could you take the latest code in CVS and check to see if it solve your
> problem ?
We took the new get_cookie() implementation from CVS and replaced the
one in our mod_jk 1.2.5 package and all hell broke loose. The jvmroute
of the JSESSIONID cookie weren't being respected and users coudn't do
anything in our load balanced setup because they were getting new
JSESSIONID cookies on each request.
We reverted very quickly so I didn't get a good chance to debug it.
Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem
with the new get_cookie() in the 1.2.5 version.
I've manually followed the new get_cookie() code and it looks right to
me but I'm nervous about it for now.
I'd like to know if anyone else has had success with the new
get_cookie() in a load balanced setup.
Sandy
mod_jk 1.2.6 release - any showstopper ?
Posted by Henri Gomez <hg...@apache.org>.
Fix the latest Bill fix on lb cookies it seems there
is nothing which prevent us from releasing jk 1.2.6.
So if nobody reports a show stopper today, I'll
start the jk 1.2.6 release tomorrow morning CET.
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Sandy McArthur <Sa...@McArthur.org>.
Bill,
Much thanks!
We've tested the fixed get_cookie back-ported to mod_jk 1.2.5 and it
works well.
We'll deploy that version into production tonight but I don't expect
any problems. I'll let y'all know if there is.
Sandy
On Jul 20, 2004, at 3:17 PM, Bill Barker wrote:
> I see that attachments are still getting stripped from the list :).
>
> The problem is yet-another-typo. The check for a comma
> cookie-delimiter
> ends up re-setting the returned cookie value to NULL, so the lb thinks
> that
> no cookie was sent. If this attachment comes through, it's the patch
> for
> it. I'll commit it later (PST), if nobody else wants it.
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Bill Barker <wb...@wilshire.com>.
I see that attachments are still getting stripped from the list :).
The problem is yet-another-typo. The check for a comma cookie-delimiter
ends up re-setting the returned cookie value to NULL, so the lb thinks that
no cookie was sent. If this attachment comes through, it's the patch for
it. I'll commit it later (PST), if nobody else wants it.
----- Original Message -----
From: "Bill Barker" <wb...@wilshire.com>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Tuesday, July 20, 2004 11:35 AM
Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie
> I was thinking something like attached.
>
> ----- Original Message -----
> From: "Sandy McArthur" <Sa...@McArthur.org>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Tuesday, July 20, 2004 7:04 AM
> Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie
>
>
> >
> > On Jul 20, 2004, at 5:27 AM, Henri Gomez wrote:
> >
> > > Could you send us you workers.properties ?
> >
> > attached.
> >
>
>
> --------------------------------------------------------------------------
--
> ----
>
>
> >
> >
> > >> If
> > >> you feel like putting more work into this, adding
> > >> 'fprintf(stderr,...)'
> > >> statements should go to the Apache error_log.
> > >
> > > Where did you want me put fprint ?
> >
> > Let us know where you want them and we'll test that code too.
> >
> > Sandy McArthur
>
----------------------------------------------------------------------------
----
>
> This message is intended only for the use of the person(s) listed above as
the intended recipient(s), and may contain information that is PRIVILEGED
and CONFIDENTIAL. If you are not an intended recipient, you may not read,
copy, or distribute this message or any attachment. If you received this
communication in error, please notify us immediately by e-mail and then
delete all copies of this message and any attachments.
>
> In addition you should be aware that ordinary (unencrypted) e-mail sent
through the Internet is not secure. Do not send confidential or sensitive
information, such as social security numbers, account numbers, personal
identification numbers and passwords, to us via ordinary (unencrypted)
e-mail.
>
>
----------------------------------------------------------------------------
----
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Bill Barker <wb...@wilshire.com>.
I was thinking something like attached.
----- Original Message -----
From: "Sandy McArthur" <Sa...@McArthur.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Tuesday, July 20, 2004 7:04 AM
Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie
>
> On Jul 20, 2004, at 5:27 AM, Henri Gomez wrote:
>
> > Could you send us you workers.properties ?
>
> attached.
>
----------------------------------------------------------------------------
----
>
>
> >> If
> >> you feel like putting more work into this, adding
> >> 'fprintf(stderr,...)'
> >> statements should go to the Apache error_log.
> >
> > Where did you want me put fprint ?
>
> Let us know where you want them and we'll test that code too.
>
> Sandy McArthur
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Sandy McArthur <Sa...@McArthur.org>.
On Jul 20, 2004, at 5:27 AM, Henri Gomez wrote:
> Could you send us you workers.properties ?
attached.
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Henri Gomez <hg...@apache.org>.
Bill Barker wrote:
> ----- Original Message -----
> From: "Sandy McArthur" <Sa...@McArthur.org>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Monday, July 19, 2004 9:15 PM
> Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie
>
>
>
>>On Jul 19, 2004, at 8:43 AM, Henri Gomez wrote:
>>
>>>And since I couldn't delay the release to long, we need a quick reply,
>>>so thanks to take a look at it.
>>
>>We've setup a current CVS checkout of mod_jk at
>>http://sp27en1.nerdc.ufl.edu/login.do which is load balancing to our
>>webmail cluster. If you constantly reload the page you'll see it's
>>setting a new JSESSIONID cookie on every request.
Could you send us you workers.properties ?
> Yup. Sending the cookie almost always fails to stick. Sending the
> jsessionid via URL-rewriting always sticks. So it does look like there is a
> bug with the lb cookie parsing. I can't see by looking at the code what it
> is however :(. I can probably find a machine that I can hook up with the
> HEAD code and lb to see what is going wrong, but I can't promise when. If
> you feel like putting more work into this, adding 'fprintf(stderr,...)'
> statements should go to the Apache error_log.
I've got such settings here, with 2 TC 3.3.2.
Where did you want me put fprint ?
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "Sandy McArthur" <Sa...@McArthur.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Monday, July 19, 2004 9:15 PM
Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie
> On Jul 19, 2004, at 8:43 AM, Henri Gomez wrote:
> > And since I couldn't delay the release to long, we need a quick reply,
> > so thanks to take a look at it.
>
> We've setup a current CVS checkout of mod_jk at
> http://sp27en1.nerdc.ufl.edu/login.do which is load balancing to our
> webmail cluster. If you constantly reload the page you'll see it's
> setting a new JSESSIONID cookie on every request.
>
Yup. Sending the cookie almost always fails to stick. Sending the
jsessionid via URL-rewriting always sticks. So it does look like there is a
bug with the lb cookie parsing. I can't see by looking at the code what it
is however :(. I can probably find a machine that I can hook up with the
HEAD code and lb to see what is going wrong, but I can't promise when. If
you feel like putting more work into this, adding 'fprintf(stderr,...)'
statements should go to the Apache error_log.
> For comparison https://webmail.ufl.edu/login.do is using mod_jk 1.2.5
> load balancing to the same webmail cluster.
>
Yup. This one will always stick with the cookie.
> Sandy McArthur
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Sandy McArthur <Sa...@McArthur.org>.
On Jul 19, 2004, at 8:43 AM, Henri Gomez wrote:
> And since I couldn't delay the release to long, we need a quick reply,
> so thanks to take a look at it.
We've setup a current CVS checkout of mod_jk at
http://sp27en1.nerdc.ufl.edu/login.do which is load balancing to our
webmail cluster. If you constantly reload the page you'll see it's
setting a new JSESSIONID cookie on every request.
For comparison https://webmail.ufl.edu/login.do is using mod_jk 1.2.5
load balancing to the same webmail cluster.
Sandy McArthur
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Henri Gomez <hg...@apache.org>.
Sandy McArthur wrote:
>
> On Jul 19, 2004, at 4:06 AM, Henri Gomez wrote:
>
>> Sandy McArthur wrote:
>>
>>> Thinking on it more, I think I'm full of it and I was confusing the
>>> symptoms of two problems that were happening at the same time.
>>> Disregard my comments below until I can double check myself.
>>> Sandy
>>> On Jul 15, 2004, at 6:01 PM, Sandy McArthur wrote:
>>>
>>>> On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote:
>>>>
>>>>> Could you take the latest code in CVS and check to see if it solve
>>>>> your
>>>>> problem ?
>>>>
>>>>
>>>> We took the new get_cookie() implementation from CVS and replaced
>>>> the one in our mod_jk 1.2.5 package and all hell broke loose. The
>>>> jvmroute of the JSESSIONID cookie weren't being respected and users
>>>> coudn't do anything in our load balanced setup because they were
>>>> getting new JSESSIONID cookies on each request.
>>>>
>>>> We reverted very quickly so I didn't get a good chance to debug it.
>>>> Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem
>>>> with the new get_cookie() in the 1.2.5 version.
>>>>
>>>> I've manually followed the new get_cookie() code and it looks right
>>>> to me but I'm nervous about it for now.
>>>>
>>>> I'd like to know if anyone else has had success with the new
>>>> get_cookie() in a load balanced setup.
>>
>>
>> I'm waiting for your reply to tag and make jk 1.2.6 release.
>
>
> I double checked our setup and our attempt to patch mod_jk 1.2.5 with
> the new get_cookie implementation and found that request were *not*
> being forward to the right clone based on the jvmroute part of the
> JSESSIONID cookie.
>
> I have not had time to test a current CVS checkout of mod_jk in a load
> balanced setup.
Well the patch was release to fix your problem and correct what could be
a serious problem in jk 1.2.x and I'd like to know if it's fixed before
making the 1.2.6 release.
And since I couldn't delay the release to long, we need a quick reply,
so thanks to take a look at it.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "Sandy McArthur" <Sa...@McArthur.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Monday, July 19, 2004 1:21 AM
Subject: Re: mod_jk 1.2.6 release ? - session tracking cookie
>
> On Jul 19, 2004, at 4:06 AM, Henri Gomez wrote:
>
> > Sandy McArthur wrote:
> >
> >> Thinking on it more, I think I'm full of it and I was confusing the
> >> symptoms of two problems that were happening at the same time.
> >> Disregard my comments below until I can double check myself.
> >> Sandy
> >> On Jul 15, 2004, at 6:01 PM, Sandy McArthur wrote:
> >>> On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote:
> >>>
> >>>> Could you take the latest code in CVS and check to see if it solve
> >>>> your
> >>>> problem ?
> >>>
> >>> We took the new get_cookie() implementation from CVS and replaced
> >>> the one in our mod_jk 1.2.5 package and all hell broke loose. The
> >>> jvmroute of the JSESSIONID cookie weren't being respected and users
> >>> coudn't do anything in our load balanced setup because they were
> >>> getting new JSESSIONID cookies on each request.
> >>>
> >>> We reverted very quickly so I didn't get a good chance to debug it.
> >>> Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem
> >>> with the new get_cookie() in the 1.2.5 version.
> >>>
> >>> I've manually followed the new get_cookie() code and it looks right
> >>> to me but I'm nervous about it for now.
> >>>
> >>> I'd like to know if anyone else has had success with the new
> >>> get_cookie() in a load balanced setup.
> >
> > I'm waiting for your reply to tag and make jk 1.2.6 release.
>
> I double checked our setup and our attempt to patch mod_jk 1.2.5 with
> the new get_cookie implementation and found that request were *not*
> being forward to the right clone based on the jvmroute part of the
> JSESSIONID cookie.
>
If the UA is sending trailing white-space between the Cookie value and the
';', then the current patch will fail. I don't know of any UAs that do,
which is why I didn't bother with stripping it (at least this close to a
release date).
> I have not had time to test a current CVS checkout of mod_jk in a load
> balanced setup.
>
> Sandy McArthur
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Sandy McArthur <Sa...@McArthur.org>.
On Jul 19, 2004, at 4:06 AM, Henri Gomez wrote:
> Sandy McArthur wrote:
>
>> Thinking on it more, I think I'm full of it and I was confusing the
>> symptoms of two problems that were happening at the same time.
>> Disregard my comments below until I can double check myself.
>> Sandy
>> On Jul 15, 2004, at 6:01 PM, Sandy McArthur wrote:
>>> On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote:
>>>
>>>> Could you take the latest code in CVS and check to see if it solve
>>>> your
>>>> problem ?
>>>
>>> We took the new get_cookie() implementation from CVS and replaced
>>> the one in our mod_jk 1.2.5 package and all hell broke loose. The
>>> jvmroute of the JSESSIONID cookie weren't being respected and users
>>> coudn't do anything in our load balanced setup because they were
>>> getting new JSESSIONID cookies on each request.
>>>
>>> We reverted very quickly so I didn't get a good chance to debug it.
>>> Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem
>>> with the new get_cookie() in the 1.2.5 version.
>>>
>>> I've manually followed the new get_cookie() code and it looks right
>>> to me but I'm nervous about it for now.
>>>
>>> I'd like to know if anyone else has had success with the new
>>> get_cookie() in a load balanced setup.
>
> I'm waiting for your reply to tag and make jk 1.2.6 release.
I double checked our setup and our attempt to patch mod_jk 1.2.5 with
the new get_cookie implementation and found that request were *not*
being forward to the right clone based on the jvmroute part of the
JSESSIONID cookie.
I have not had time to test a current CVS checkout of mod_jk in a load
balanced setup.
Sandy McArthur
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Henri Gomez <hg...@apache.org>.
Sandy McArthur wrote:
> Thinking on it more, I think I'm full of it and I was confusing the
> symptoms of two problems that were happening at the same time. Disregard
> my comments below until I can double check myself.
>
> Sandy
>
> On Jul 15, 2004, at 6:01 PM, Sandy McArthur wrote:
>
>> On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote:
>>
>>> Could you take the latest code in CVS and check to see if it solve your
>>> problem ?
>>
>>
>> We took the new get_cookie() implementation from CVS and replaced the
>> one in our mod_jk 1.2.5 package and all hell broke loose. The jvmroute
>> of the JSESSIONID cookie weren't being respected and users coudn't do
>> anything in our load balanced setup because they were getting new
>> JSESSIONID cookies on each request.
>>
>> We reverted very quickly so I didn't get a good chance to debug it.
>> Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem
>> with the new get_cookie() in the 1.2.5 version.
>>
>> I've manually followed the new get_cookie() code and it looks right to
>> me but I'm nervous about it for now.
>>
>> I'd like to know if anyone else has had success with the new
>> get_cookie() in a load balanced setup.
I'm waiting for your reply to tag and make jk 1.2.6 release.
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: mod_jk 1.2.6 release ? - session tracking cookie
Posted by Sandy McArthur <Sa...@McArthur.org>.
Thinking on it more, I think I'm full of it and I was confusing the
symptoms of two problems that were happening at the same time.
Disregard my comments below until I can double check myself.
Sandy
On Jul 15, 2004, at 6:01 PM, Sandy McArthur wrote:
> On Jul 15, 2004, at 3:05 AM, Henri Gomez wrote:
>
>> Could you take the latest code in CVS and check to see if it solve
>> your
>> problem ?
>
> We took the new get_cookie() implementation from CVS and replaced the
> one in our mod_jk 1.2.5 package and all hell broke loose. The jvmroute
> of the JSESSIONID cookie weren't being respected and users coudn't do
> anything in our load balanced setup because they were getting new
> JSESSIONID cookies on each request.
>
> We reverted very quickly so I didn't get a good chance to debug it.
> Tomorrow we'll test mod_jk from CVS to make sure it wasn't a problem
> with the new get_cookie() in the 1.2.5 version.
>
> I've manually followed the new get_cookie() code and it looks right to
> me but I'm nervous about it for now.
>
> I'd like to know if anyone else has had success with the new
> get_cookie() in a load balanced setup.
>
> Sandy