weblogic persistenca does not works

Sorry this is so late, must have missed the alert, hopefully you found it, if not you simply need to create a cookie profile using a hash, for the cookie name use JSESSIONID. The cluster does not determine whether or not you use a JSESSIONID, most containers use them, unless turned off, which no one should do unless they are storing the session information in a different cookie.

 

 

Create the cookie hash profile, specify the JSESSIONID as the cookie name, if there is a specific length that the cookie has you can specify that in the length value, I usually just leave them offset and length set to the defaults, works better that way, so if the cookie entropy ever changes you don't have to change the profile.

 

 

Apply the new persistence profile to your VIP, if you want a timeout value for the cookie, make sure you set that in the profile as well.

 

 

The F5 will look in the header for the JSESSIONID as a cookie, if it is not there it will send the request to the server, inspect the server header response, find the JSESSIONID cookie, and hash it and store the value in a persistence table which it will lookup to see which cookie came from which server, very cool stuff.

 

 

If the header has the cookie it will look in the persistence table for it, if it's not there, it's probably a stale session, so it will send it to the next server in the LB pool and if the ID changes, hash that in the persistence table, if it stays the same, it...guess? Yes of course, hashes that as well. ;-)

 

 

Let me know how it went/goes.