My Oracle Support Banner

Reconnect to SSO Server is Almost Impossible After Idle Time (Doc ID 454888.1)

Last updated on MARCH 01, 2023

Applies to:

Oracle Application Server Single Sign-On - Version 10.1.2.0.2 and later
Information in this document applies to any platform.

Symptoms

After some period of inactivity, reconnection to the SSO-Server is not possible.

Although Global Inactivity Timeout (GITO) is not configured, the SSOServer.log shows the following entries:

Wed Aug 08 12:32:38 CEST 2007 [DEBUG] AJPRequestHandler-ApplicationServerThread-23 DirContextPool: Connection last used: Wed Aug 08 12:25:18 CEST 2007, idle timeout period: 1
Wed Aug 08 12:32:38 CEST 2007 [DEBUG] AJPRequestHandler-ApplicationServerThread-23 DirContextPool: Current time: Wed Aug 08 12:32:38 CEST 2007, Connection maxidle time: Wed Aug 08 12:26:18 CEST 2007
Wed Aug 08 12:32:38 CEST 2007 [DEBUG] AJPRequestHandler-ApplicationServerThread-23 Can NOT use pooled connection.
Wed Aug 08 12:32:38 CEST 2007 [DEBUG] AJPRequestHandler-ApplicationServerThread-23 DirContextPool: Entered close ... method
Wed Aug 08 12:32:38 CEST 2007 [DEBUG] AJPRequestHandler-ApplicationServerThread-23 DirContextPool: Connection reached idle timeout limit. Trying next...
Wed Aug 08 12:32:38 CEST 2007 [DEBUG] AJPRequestHandler-ApplicationServerThread-23 DirContextPool: Creating a brand new OID connection

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
References


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