During Side-by-Side Deployment, Inactive Sessions Appear Not to Be Removed by WebLogic Server Container
(Doc ID 1542640.1)
Last updated on NOVEMBER 14, 2022
Applies to:Oracle WebLogic Server - Version 10.3.1 and later
Information in this document applies to any platform.
During side-by-side deployment, after the first version of the application is deployed (v1), all sessions are served by v1. When the second version of the application (v2) is deployed, all new HTTP sessions are served by v2.
It appears that any HTTP sessions served by v1 are lost when v2 is deployed. However, this is not true. These sessions are inactive and are not removed until the session timeout is reached. When the retire-timeout for v2 occurs, these inactive sessions are forced to close.
This is also noticed when we rollback to v1, i.e., redeploy the v1 application: it appears that all sessions served by v2 are lost.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document