My Oracle Support Banner

Stuck Threads On WCC/UCM Managed Servers At GET /adfAuthentication request on SAML2/Okta Integration (Doc ID 2847293.1)

Last updated on FEBRUARY 07, 2022

Applies to:

Oracle WebCenter Content - Version and later
Information in this document applies to any platform.


WebCenter Content (WCC) managed server(s) show stuck threads on a fairly regular basis.

Sometimes a "Service Unavailable" page is displayed, but other times do get to the login page. All the while, in the HTTP browser trace that it’s getting stuck on /adfAuthentication request.

The environment consists of SAML 2.0 with an Okta integration configured on a non-cloud based server which in turn fetches user information from the Microsoft Active Directory (AD).

From UCM_server1.out:

<Jan 4, 2022 7:58:26,983 AM PST> <Emergency> <oracle.dfw.incident> <BEA-000000> <incident 69 created with problem key "BEA-000337 [/adfAuthentication]">
<Jan 4, 2022 7:59:26,394 AM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "690" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@28c38be4[GET /adfAuthentication]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
    java.lang.Object.wait(Native Method)
    netscape.ldap.LDAPMessageQueue.waitForMessage(Unknown Source)
    netscape.ldap.LDAPMessageQueue.waitFirstMessage(Unknown Source)
    netscape.ldap.LDAPConnection.sendRequest(Unknown Source)
    netscape.ldap.LDAPConnection.add(Unknown Source)
    netscape.ldap.LDAPConnection.add(Unknown Source)
    netscape.ldap.LDAPConnection.add(Unknown Source)
    sun.reflect.GeneratedMethodAccessor522.invoke(Unknown Source)
    com.sun.proxy.$Proxy89.process(Unknown Source)$

1. Open the We Content page ina browser.
2. This forwards the login request via WebLogic (WLS) to initiating a successful SAML login.
3. Log-in and close without logging off.
4. After an hour or so (especially when the traffic is low), open a new browser to log onto WCC and click on login.
5. It will spin for 3-5 minutes and either "Service Unavailable" error is displayed or sometimes the SAML login page is displayed.

Admin(s) are noticing stuck threads on UCM managed servers on the two-node cluster even when there is low traffic and user(s) either gets the "Service Unavailable" error page or gets to the SAML login page after 3-5 minutes.




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.