BugRat Report #603 has been filed.

[BugRat Mail System]

Bug report #603 has just been filed.

You can view the report at the following URL:

   <http://znutar.cortexity.com/BugRatViewer/ShowReport/603>

REPORT #603 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2
   JVM Release: 1.3
   Operating System: Linux 
   OS Release: 6.2?
   Platform: Intel

Synopsis: 
mod_jk fails to route according to JSESSIONID cookie

Description:
When using a number of tomcats with the balance mechanism of mod_jk, subsequent 
requests to the server are not necessarily routed to the same tomcat. The old 
mod_jserv worked fine for us.
This happens sometimes when other cookies are sent to the server along with the 
JSESSIONID cookie.

The bug is in the way the session route is searched in get_most_suitable_worker 
funtion in jk_lb_worker.c file - the programmer assumed that there is nothing in the 
string after the value of JSESSIONID

Title: BugRat Report # 603

BugRat Report # 603

Project: Tomcat	Release: 3.2
Category: Bug Report	SubCategory: New Bug Report
Class: swbug	State: received
Priority: high	Severity: critical
Confidence: public

Submitter: Boaz Shaham ( [EMAIL PROTECTED] )
Date Submitted: Dec 17 2000, 12:57:09 CST
Responsible: Z_Tomcat Alias ( [EMAIL PROTECTED] )

Synopsis:

mod_jk fails to route according to JSESSIONID cookie

Environment: (jvm, os, osrel, platform)

1.3, Linux , 6.2?, Intel

Additional Environment Description:

Report Description:

When using a number of tomcats with the balance mechanism of mod_jk, subsequent requests to the server are not necessarily routed to the same tomcat. The old mod_jserv worked fine for us. This happens sometimes when other cookies are sent to the server along with the JSESSIONID cookie. The bug is in the way the session route is searched in get_most_suitable_worker funtion in jk_lb_worker.c file - the programmer assumed that there is nothing in the string after the value of JSESSIONID

Workaround:

null

View this report online...