Re: [PATCH] adapter in load balancing (version 1.2 - Tomcat 3.2.x)

[Dan Milstein]

Benoit,

Thanks -- I actually just fixed this in the 3.2 branch.

-Dan

Benoit Derouet wrote:
 
 Hi,
 
 The load balancer worker fail to handle load balancing (with sticky
 sessions) if the application uses custom cookies.
 
 In some circumstances, the load balancer worker can't retreive the server
 name from the JSessionID cookie and is not able to redirect to the good
 server.
 
 The algorithm parse the cookie header to extract the server name from the
 JSessionID cookie. It find properly the end of the server name but fail to
 cut the chars after.
 So, it works fine if the cookie header contains only one cookie (or if
 JSessionID is the last cookie) but If they are custom cookie, the server
 name extracted will be: "servername;mycookieVal=myCookieValue .."
 
 The bug is fixed around line 170.
 (line id_end=NULL; replaced by id_end[0] = '\0'; )
 
 'hope this will be integrated in future versions ! (as our customers need
 sticky load balancing...)
 
 regards.
 
 Benoit
-- 

Dan Milstein // [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: [PATCH] adapter in load balancing (version 1.2 - Tomcat 3.2.x)

[GOMEZ Henri]

Will you update also the 3.3 branch ?-)

"Pour la plupart des hommes, se corriger consiste  changer de dfauts."
-- Voltaire 

-Original Message-
From: Dan Milstein [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 12, 2001 6:59 PM
To: [EMAIL PROTECTED]
Subject: Re: [PATCH] adapter in load balancing (version 1.2 - Tomcat
3.2.x)


Benoit,

Thanks -- I actually just fixed this in the 3.2 branch.

-Dan

Benoit Derouet wrote:
 
 Hi,
 
 The load balancer worker fail to handle load 
balancing (with sticky
 sessions) if the application uses custom cookies.
 
 In some circumstances, the load balancer worker 
can't retreive the server
 name from the JSessionID cookie and is not able to redirect 
to the good
 server.
 
 The algorithm parse the cookie header to extract the 
server name from the
 JSessionID cookie. It find properly the end of the server 
name but fail to
 cut the chars after.
 So, it works fine if the cookie header contains only one 
cookie (or if
 JSessionID is the last cookie) but If they are custom 
cookie, the server
 name extracted will be: "servername;mycookieVal=myCookieValue .."
 
 The bug is fixed around line 170.
 (line id_end=NULL; replaced by id_end[0] = '\0'; )
 
 'hope this will be integrated in future versions ! 
(as our customers need
 sticky load balancing...)
 
 regards.
 
 Benoit
-- 

Dan Milstein // [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]