My Oracle Support Banner

Sessions are Terminated at 8 Hours After Upgrade To PS3 (Doc ID 2164492.1)

Last updated on SEPTEMBER 14, 2023

Applies to:

Oracle Access Manager - Version 11.1.2.3.0 to 11.1.2.3.5 [Release 11g]
Information in this document applies to any platform.

Symptoms

After upgrading from PS2 BP04 to PS3 BP05, sessions are cut of at exactly 8 hours after having logged in, despite the fact that Expiry time is set to 15 hrs.

This is happening only in HA environment, when both nodes are up.

Checking in the oam-config.xml "Expiry" is set to 15h:
<Setting Name="Expiry" Type="htf:timeInterval">900 M</Setting>

while in the database sessions get created with the expected duration (15hrs), then they get reset to the default value of 8 hrs:

SQL> select USERID, CRED_TIMEOUT_INTERVAL, TIMEOUT_INTERVAL, CREATE_TIME, EXPIRY_TIME, sessionid from fmw_oam.oam_session

returns:

user1 57600 18000 21/06/16 07:56:34,973000000 21/06/16 22:56:34,973000000 c36ab3cf-a46a-4b18-a9d8-808880b3182d|SuvLIdTaHgyOkiDC4Wv026p5PSo=

while using the session for a while, the expiry time has suddenly changed to 15:5x:xx instead of 22:5x.xx :

user1 57600 18000 21/06/16 07:56:34,973000000 21/06/16 15:56:34,973000000 c36ab3cf-a46a-4b18-a9d8-808880b3182d|SuvLIdTaHgyOkiDC4Wv026p5PSo=

Changes

 Upgrade from PS2 to PS3.

Cause

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
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.