Forum Discussion
smp_86112
Cirrostratus
CirrostratusWeblogic JSessionID Persistence
A customer of mine found this article, which uses JSessionID for WebLogic persistence:
http://support.f5.com/kb/en-us/solu...l7392.html
But I am having a difficult time understanding why Cookie persistence would not accomplish exactly the same thing? If the client can accept a JSessionID cookie, then I think it is safe to assume it can accept an LTM cookie. Assuming that's true, is there some other reason why Cookie persistence wouldn't work too?
hooleylistI agree with you. The only reason I can think of for using UIE persistence based off of an application cookie value is if you want to persist across virtuals/pools/services (which the cookie insert persistence profile doesn't support).
Cookie insert persistence is simpler and more efficient for TMM versus mapping app cookie values to a server in its own memory.
Aaron
smp_86112Thanks hoolio, I just needed that sanity check to make sure I wasn't missing something obvious. It also makes sense intuitively that it is more efficient to use Cookie persistence. Thanks for the feedback.