You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Jerome Waibel <sc...@schlund.de> on 2000/05/22 19:48:54 UTC

mod_jserv/6108: JservSessionId ist not found in Query -> Loadbalancing fails when cookies are not used

>Number:         6108
>Category:       mod_jserv
>Synopsis:       JservSessionId ist not found in Query -> Loadbalancing fails when cookies are not used
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon May 22 10:50:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     schrom@schlund.de
>Release:        1.3.9
>Organization:
apache
>Environment:
Linux 2.2.14, mod_jserv 1.1.1, ibm jdk118
>Description:
Since mod_jserv 1.1.1 get_param() in jserv_balance.c scans r->uri instead
of r->args for the JServSessionId. But the Uri does not contain the
Request-Params, the SessionId is not found. Thus the load balancer can not
determine the correct ajpv-Server, load balancing fails. This happens
only if you don't use cookies and have the Session URLencoded.
>How-To-Repeat:
Do some load balancing without(!) cookies, it will fail, sessions will not be
continued.
>Fix:
The old code from 1.1 (which is still there, but commented out) works
fine.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]