Why Do Siebel Web Client Sessions Fail To Time Out Even Though the SessionTimeout Parameter Is Set?
(Doc ID 477544.1)
Last updated on JULY 10, 2023
Applies to:
Siebel System Software - Version 8.0.0.1 SIA [20408] to 16.18 [IP2016] [Release V8 to V16]Siebel CRM - Version 8.0.0.1 SIA [20408] to 16.18 [IP2016] [Release V8 to V16]
Information in this document applies to any platform.
*** Currency Review 15-DEC-2017 Some information no longer applicable for IP2017 ***
Goal
This knowledge document describes the scenarios where the expected behavior is that the Siebel Web Client session will not automatically time out, even though the session has been inactive for a period of time greater than the duration specified by the SessionTimeout parameter. The SessionTimeout parameter is discussed in more detail in the following Siebel Bookshelf references:
Siebel Bookshelf version 8.x > Siebel System Administration Guide > Structure of the eapps.cfg File.
Solution
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
| Goal |
| Solution |
| Application Message Bar Update Interval Versus SessionTimeout |
| User Enabling the Application Message Bar |
| Alarm Manager Load Frequency Versus SessionTimeout |
| PushKeepAliveTimer Versus SessionTimeout |
| Customized Request from Web Client to Application Server Versus SessionTimeout |