Hi Paul,
Can you provide me with complete response received at browser? This will
help me understand what can be the issue.
Also turn on monitoring in load-balancer xml. Provide web-server logs as
well.
Thanks,
Kshitiz
pgribben wrote:
> Hi Kshitiz
>
> Thanks for the info. I had an older version of the loadbalancer
> (aslb-9.1.1-b9) which doesn't have the rewrite-cookies property so I
> upgraded to aslb-9.1.1-b13 and can see that the DTD now accepts property
> 'rewrite-cookies'.
>
> Unfortunately, dispite setting the property to true in loadbalancer.xml the
> behaviour is as before. Any other thoughts?
>
> Regards
> Paul
>
>
> Kshitiz Saxena wrote:
>
>> Hi,
>>
>> In load-balancer xml, you will see rewrite-cookies as property. Please
>> set it to true. I assume by default it is false.
>>
>> Thanks,
>> Kshitiz
>>
>> pgribben wrote:
>>
>>> Hi,
>>>
>>> I've got SJSWS load balancing requests to a web-app on a Glassfish 2.1
>>> cluster (consisting of 2 instances). The app consists of a servlet that
>>> replies with the request.getServerName(), request.getServerPort() and the
>>> servletContext's computed realPath(".") value. I would expect successive
>>> calls from the same browser window to 'land' on the same GF instance, but
>>> infact am finding that instead the requests land alternately on each
>>> instance (i.e. round-robin). I've checked the HTTP request headers and in
>>> every case the same JSESSIONID value is in use.
>>>
>>> I also tried changing the policy in loadbalancer.xml from round-robin to
>>> weighted-round-robin but the behaviour is unchanged.
>>>
>>> Any help would be greatly appreciated,
>>>
>>> Thanks
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>>
>>
>
>