My Oracle Support Banner

<Error> <WebLogicServer> <BEA-000337> <[STUCK] Users Not Able To Login (Doc ID 2137710.1)

Last updated on AUGUST 31, 2020

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.3.1 and later
Information in this document applies to any platform.

Symptoms

On :  2.3.1 version, SW - System Wide

Environment upgraded to jdk1.6.0_45/WebLogic Server 10.3.6.0 and ojdbc5-11.2.0.3.0.jar.
Applications nodes get stuck and not able to proceed further.This env is integrated with OSB miiddleware and many external system are configured with SSO. OSBUSER is middleware user which is required for CCB Integration with external system.

Actual behavior
----------------
Every other day the following error clotting the logs is making the application unusable.

ERROR
-----------------------
Feb 3, 2016 10:11:50 AM AST> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "673" seconds working on the request "Http Request: /spl/portal", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-47 "[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
   com.splwg.base.support.cobol.host.sockets.UnixDomainSocketNative.readFromSocket(UnixDomainSocketNative.java:???)

Expected Behavior
------------------------
Users are able to login and the application to be stable.

Changes

 

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
Changes
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.