<Error> <WebLogicServer> <BEA-000337> <[STUCK] Uusers not able to login

(Doc ID 2137710.1)

Last updated on OCTOBER 17, 2017

Applies to:

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


On :  2.3.1 version, SW - System Wide

Environment upgraded to jdk1.6.0_45/WebLogic Server and ojdbc5-
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.

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> {

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

After getting this above error on the ccb weblogic logs users are not able to login and application goes down while doing several times of re-start which took more than an hour it comes back to track on our Production applications and its happen on both nodes same times


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