DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=32874>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32874 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2005-06-16 10:54 ------- Hello! I have found the source of this error (or at least why it happend to me). The source of the error was the loadbalancing. We have two servers in a cluster and we use sticky sessions. The error in the load balancing was that the answer from the server was misinterpreted by the load balancing software, when the server said it was ok, the load balancing thought the server was down. So, the first call to the application went to server A where a session was established. On the next call the load balancing would ask server A if it was ok to receive a call. Server A would reply ok, and the loadbalancing would misinterpret that assume server A was not ok. Thus, the call went to server B. In server B there was no session for the user. Since there was no session object a new empty session object was created and given to the servlet. But the bean that the servlet expected to find in the session was not there. Thus the error. Best regards! /Daniel Patrickson -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
