Why SAI Connection pool closes Object Manager connection while SessionTimeout is not reached?
Last updated on FEBRUARY 28, 2018
Applies to:Siebel CRM - Version 126.96.36.199  and later
Information in this document applies to any platform.
When using Siebel Application Integration (SAI) for Oracle Fusion Middleware for Siebel Inbound Web Services,
one has observed that SAI Siebel Resource Adapter connection pool has explicitly closed opened connections to Siebel Object Manager (EAI Object Manager).
The closed connections were on idle, however the session timeout , configured by the Resource Adapter deployment (and confirmed in the Siebel Object Manager log when its task was starting) was not reached.
For example a connection was closed after being in idle for few minutes after successful completion of a Web Service call, while SessionTimeout parameter was set to permit the idle state for over 24 hours (86400 seconds).
Below is sample EAI Object Manager log snippet, that illustrates the observed behaviour:
The behaviour was un-desired, since customer wanted to keep the Siebel Object Manager session online to immediate reediness to process new Web Service calls within given time.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms