My Oracle Support Banner

OAM 11g: SSO Login Hangs / Produces Timeout Error With Stuck Thread / auth_cred_submit (Doc ID 1377415.1)

Last updated on OCTOBER 09, 2019

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.


Intermittent Oracle Access Manager 11g (OAM) SSO login failure / WebLogic stuck thread issue in OAM 11g environment.

After OAM 11g has been running for some time (could be half an hour or 4 hours, no regularity, no pattern), after submitting credentials in the OAM login page the browser just works...... then eventually a timeout error is displayed when the WebLogic Server reaches Stuck Thread Max Time and gives up.

If 'kill -3 <pid>' is run on the OAM managed server Process ID (PID) then the OAMMgdServerName.log file shows that OAM Server is waiting for response from the LDAP Server.

Example log entries:

<Aug 11, 2011 8:25:16 PM SGT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "235" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@4f8e0de7[
POST /oam/server/auth_cred_submit HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/, application/, application/msword, application/x-ms-application, application/x-ms-xbap, application/, application/xaml+xml, */*
Referer: https://<OAM_HOSTNAME>:<PORT>/pages/login.jsp?request_id=-8104348353696688194
Accept-Language: en-us
Content-Type: application/x-www-form-urlencoded
UA-CPU: x86
]", which is more than the configured time (StuckThreadMaxTime) of "120" seconds. Stack trace:
java.lang.Object.wait(Native Method)

At the server side the thread is stuck. Nothing is printed out in log file until the WebLogic Server StuckThreadMaxTime exceeds. WebLogic server self-tuning thread will terminate that stuck thread and print out its information.

After the stuck thread is terminated, the OAM Server starts serving OAM login requests again. Users can login again.

Steps to reproduce

1. Start OAM and WebGate webserver, everything works fine.

After some time e.g. 30 minutes, 4 hours, no regularity, no pattern, users start getting timeout errors when performing SSO login:

2. At the client side, user submits user id and password in the OAM SSO login page
3. The browser keeps loading and loading, eventually a timeout page is displayed. This behavior continues for a while even if browser is closed and a new one opened.
4. When the WebLogic Server StuckThreadMaxTime exceeds, WebLogic server self-tuning thread terminates the stuck thread
5. After the stuck thread is terminated, the OAM Server starts serving OAM login requests again. Users can login again.


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

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