Mantis - Resin
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1346 minor always 09-12-06 11:24 09-27-06 12:32
Reporter: sergek Platform:  
Assigned To: ferg OS:  
Priority: normal OS Version:  
Status: closed Product Version: 3.0.18  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.0.22  
Summary: 0001346: cookie-append-server-id uses index that is off by 1
Description: I've started to use apache mod_proxy_balancer and am rolling out the <cookie-append-server-id /> flag to give mod_proxy_balancer to make the sessions sticky the way Resin asks. There is a small bug in that the appended id is one less than what is specified in that srun conf. For example, this block:

<cluster>
  <srun index="1" .... />
</cluster>

would create a jsessionid "a<randomstuff>.0" rather than .1. This is a bit confusing because you'd expect the index you specify in resin would match the index you need to set in the load balancer.
Steps To Reproduce:
Additional Information: Resin 3.0.18 on Java 5, JDBC cluster.
Relationships
Attached Files:

Notes
(0001511)
ferg   
09-13-06 13:50   
Does mod_proxy_balancer use zero-based or one-based dispatching? The <cookie-append-server-id> assumed mod_proxy_balancer wanted zero-based dispatching.
(0001516)
sergek   
09-13-06 21:29   
It doesn't use indexing. The suffixes could be "kyle" "cartman" "kenny" and "stan".
(0001529)
sergek   
09-26-06 10:12   
Just to clarify the issue

srun-index="1" -> cookie prefix="a" -> cookie suffix="0". This makes it painful to compare resin.conf and httpd.conf since the srun-index (what's in resin.conf) and the cookie-suffix (what's in httpd.conf) do not match.
(0001530)
ferg   
09-27-06 12:32   
server/01l4