Holding the reference in the HttpSession is the right thing to do. If your
load balancer does not handle this situation correctly, then it is broken.
The HttpSession state should be maintained even if requests are sent to
different web servers by the load balancer.
>From: Harris Chris <[EMAIL PROTECTED]>
>Reply-To: A mailing list for Enterprise JavaBeans development
><[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: where to hold the Session Bean's reference
>Date: Mon, 8 Jan 2001 14:58:16 -0600
>
>Hi, All.
>
> I have a stateful session bean and i'm holding all client information
>in
>the beans instance variable. If i use a load balancer to handle my web
>request, how can i identify the same session bean across requests and where
>can i store the bean's reference. I think holding the reference in the jsp
>session doesn't work out here.
>
>Please suggest me what are the other ways of doing this.
>
>bye
>diwan
>_________________________________________________________________
>Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff EJB-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
