We are using the following configuration in the load balancer setup.
- Weblogic 6.1 with a cluster having two servers - The cluster node and both the servers are running on the same machine. - Apache 2.0 server with the proxy plugin for weblogic on another machine. - We are using HttpSession based session tracking in the application.
Problem We are facing a problem with the session stickyness - Sometimes we see that the apache server redirects the user to the server which was NOT initially serving the user request... and hence the user gets kicked out from the initial session.
Our Restrictions We can not use any type of session replication since the architecture of the application doesn't support it (Objects that we keep in session are not Serializable) . We need a round robin load balancing to balance the load on the servers to have a better performance. However, once a client establishes a session between a given server we need the same server to serve the client. The plugin should NOT switch the client to the other server.
Could you please put some thoughts .. to find out what could be the issue ??
Automatically out of the box the WebLogic Plugin should demostrate a "sticky" behavior so this is somewhat odd. Do all your Apache Servers point to all available WebLogic instances (ie. a sever wasn't left out in one of the lists)? Do you see any pattern to this? Are you losing the JSESSION cookie on the client? Is possibly a misinterpretation and the user's session is expired and therefore this behavior is expected?
Off-hand I don't really have a good response for this...
Joined: Jul 18, 2001
Are you using cookies or url parameters to maintain the session id?