Replacing the WebSphere Apache Plugin with iRules
Published Jul 29, 2008
Version 1.0Was this article helpful?
One point though. There is a problem with using the iRule to use the JSESSION cookie for session persistence in the case where you have multiple pools. An fairly easy modification to that iRule is instead of using the full cookie as the persist key is to only use the 1st 26 positions, all the way up to the ":".
The issue is that the cookie has the jessionid that is unique to this session and then a unique identifier is added to the end for each WebSphere server you end up using. With two pools you have two servers. So as you get switched to another server the cookie value changes.
We have four pools, so you could get sent to four different servers. Each server tags the end of the JSESSION cookie with their unique id and thus the cookie value gets changed.
This all assumes that the WebSphere Servers are setup to share the JSESSION cookie. If they are not, then you get into real trouble.