Yes you're right. That is sufficient.
Thanks
Paul
Kshitiz Saxena wrote:
>
> Hi Paul,
>
> I am not sure what you mean by creating session state. In my view call
> to HttpServletRequest.getSession(true) will be sufficient.
>
> Thanks,
> Kshitiz
>
> pgribben wrote:
>> Kshitiz.
>>
>> I hadn't realized that I needed to set some session state to get the app
>> server to write a cookie to the response header. I set a session
>> attribute
>> in my test servlet and now the requests are sticky.
>>
>> Thanks for your help with this.
>> Paul
>>
>>
>> Kshitiz Saxena wrote:
>>
>>> Hi Paul,
>>>
>>> Thanks for the information. It was really useful.
>>>
>>> It looks like that your application is not creating any session. There
>>> is no "Set-Cookie" header in response to indicate that a session is
>>> created. Your browser is somehow sending JSESSIONID. I am not sure how
>>> that cookie was set. Please create a session in your servlet, then
>>> web-container will stamp JSESSIONID in response. Then will force
>>> load-balancer to insert additional sticky information.
>>>
>>> Thanks,
>>> Kshitiz
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>
--
View this message in context: http://old.nabble.com/Load-Balancer-routing-not-sticky-on-SJSWS-tp26577386p26594235.html
Sent from the java.net - glassfish users mailing list archive at Nabble.com.