Matt,
I have an I-rule that I wrote to successfully persist on JSESSIONID. The issue I am having is that we mirror our weblogic sessions to a fallback server. In order to use this fallback feature while loadbalancing your bea servers with F5 is being able to write an i-rule to grab the JSESSIONID and split it into 3 values cookie, Primary Server, Secondary Server. The catch is that the Primary and Secondary Server Ip, Port is hashed. I'm not real sure that there is a way to decode this hash. So my next thought was to figure out what hash value goes with what IP and hardcode those ip's in the i-rule. The only problem with this is that the hash values change every time you restart the server so that is not a good solution.
My question is has anyone seen this, or have been down this road successfully or unsuccesfully.
Thanks,
Brett