David Mossakowski wrote:
> Greetings,
>
> I should be more specific in my question.
>
> The precise thing I'm worried about is that when a session is being kept
> by the servlet engine and it is updated to fit the user's liking (simple
> search, blue background, vector of previous search results, etc.) then
> when load balancing comes in you are not guaranteed that the next
> request from that user will come to the same engine as the previous
> one. With that in mind how does one keep the session consistent?
>
> How do you go about this problem? Does anyone have a load balancer on a
> servlet application?
>
> Thanks,
> dave.
>
Since the servlet API spec is silent on this issue, the answer will be
specific to each implementation.
Apache JServ 1.0 includes load balancing code that deals with this by
directing all requests with the same session ID to the same distributed JVM
instance. No attempt is made to migrate a session from one instance to
another once it has been created, so the problems you describe above will not
occur.
Requests without a session identifier are randomly distributed among the
available instances, and you can influence this by assigning weights to bias
more, or fewer, requests to particular instances.
>
> --
> David Mossakowski [EMAIL PROTECTED]
> http://www.dwdog.com/styk 212.310.7275
>
Craig McClanahan
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
