Siebel Timeout Is Not Working in IP17 After Changing the Active Session Timeout Parameter
(Doc ID 2364611.1)
Last updated on SEPTEMBER 01, 2023
Applies to:
Siebel CRM - Version 17.4 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
In Siebel IP17, the Active Session Timeout Value (seconds) was changed from 900s to 9000s in the application interface profile in SMC and the profile was deployed accordingly.
The sessions are not timing out and it looks like the Active Session Timeout is still set to 900 seconds.
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 |
Cause |
Solution |