Forum Discussion
Irule for jsession ID weblogic support
An early assumption might be that persistence is failing. A single live server wouldn't have persistence issues (all traffic goes to it by default), but multiple live servers suggests that the transactions might be flipping between the servers causing an application error.
If these are browser sessions, the easier and more reliable approach may be to switch to standard cookie persistence.
If these are not browser sessions, then you'll need to revisit how the iRule interacts with the client and server. For example:
-
The HTTP_RESPONSE event resets the uie persistence value every time it sees a JSESSIONID Set-Cookie header from the server. Validate that the server isn't sending multiple JSESSIONID cookies with different values.
-
The HTTP_REQUEST event has a log entry that displays the results of a uie lookup. For any given client does this value change?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com