Siebel IP2017 And Later: Active Session Timeout Increase Is Causing Tasks Max-out Issue Due To Guest Session Timeout (Doc ID 2652910.1)

Last updated on AUGUST 13, 2023

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
After increasing the Active Session Timeout value from 900 to 43000, the MaxTasks parameter is reached and new users sessions can't connect to application as Guest sessions used to render the login screen is not getting terminated after 300 seconds causing the MaxTasks issue.

 
EXPECTED BEHAVIOR
-----------------------
Guest sessions should be terminated after reaching the 300second value specific in Application Interface (AI) profile for a specific Application Object Manager (AOM)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. In Siebel Management Console (SMC) for the Application Interface (AI) profile, set the below values:

Active Session Timeout - 43000
Login Session (Guest Session) Timeout - 300

2. Check to see if the guest sessions are closed in 300 seconds
3. Connect using server manager and do a list tasks to see if the sessions are completed by logging into application and creating multiple sessions.

Changes

Cause

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