Skip to main content

Stuck & Hogging Threads, How to deal with STUCK & HOGGING Threads.

 STUCK thread?

We know that a STUCK thread is a thread which is processing a request for more than maximum time defined for a thread to complete the request which is default 600 and can be configured from admin console.  Based on different technical circumstances like due to some intermittent issues with network, database, application server etc a STUCK can be release after some time, but most of the time is certain thread or threads declared as STUCK then there would be some problem either temporary or permanent which need some fix.

How to deal with STUCK thread?

As of now there is no way to deal with a STUCK thread like, sometime end users ask if there any way to kill STUCK thread. No, there is no way to deal with STUCK thread.

To deal with STUCK thread –

·                     Take multiple thread dumps immediately.
·                     Review thread dumps or from console (managed server > monitoring > threads) Where it exactly got stuck?
·                     See how many threads got stuck?
·                     If the stuck thread count is increasing or constant?
·                     If constant then if got stuck on same area (application code etc ) or at different places ?
·                     If getting increase then there would be some serious problem and you have to do a quick health check of youapplication server, database and other integrated technologies wherever your application reaching like ldap server for authentication, some other API’s or web services etc, and in parallel review thread dumps for STUCK threads and share same with your developers to analyze quickly.
·                     If you have one, two or few constant STUCK threads and it’s not increasing then you can monitor it for some more time to check if they get clear or not, if not then to clear them you have only option to restart your managed server(s), and its better to restart and clear them before they make further any impact. 
Hogging thread?

I am sure if you are going to read this post then you must aware about what is hogging thread. Ok, let me define it again in a single line, “I hogging thread is a thread which is taking more than usual time to complete the request and can be declared as STUCK”.

Comments

Post a Comment

Popular posts from this blog

oracle.ohs.plugin.nodemanager.OhsProcessManagementPlugin$ProcessImpl buildIoException SEVERE: Failed to start the server ohs1 In New Installation of FMW 12.2.1.3 on Windows Server

Problem Summery: When we are trying start OHS instance it's failing with an error. Error: 29 Mar, 2018 10:30:22 PM IST> <INFO> <Server Implementation Class: weblogic.nodemanager.server.NMServer$ClassicServer.> <29 Mar, 2018 10:30:23 PM IST> <INFO> <Secure socket listener started on port 5556> <29 Mar, 2018 10:30:54 PM IST> <INFO> <base_domain> <ohs1> <Creating directory "F:\OHS\user_projects\domains\base_domain\system_components\OHS\ohs1\data\nodemanager"> Mar 29, 2018 10:30:54 PM oracle.ohs.plugin.nodemanager.OhsProcessManagementPlugin$ProcessImpl start INFO: Starting server ohs1 Mar 29, 2018 10:30:55 PM oracle.ohs.plugin.nodemanager.OhsRunCommand execute INFO: Running F:\OHS\ohs\bin\launch.exe F:\OHS\ohs\bin\httpd.exe -DOHS_MPM_WINNT -d F:/OHS/user_projects/domains/base_domain/config/fmwconfig/components/OHS/instances/ohs1 -f F:\OHS\user_projects\doma ins\base_domain\config\fmwconfig\c...
Post a Comment
Read more

Node Manager Username and Password for Oracle HTTP Server 12c in a Standalone Domain

Start the Ohs Instance for 12C F:\OHS\user_projects\domains\base_domain\bin>stopComponent.cmd ohs1 Step:1 Stop the OHS component F:\OHS\user_projects\domains\base_domain\bin>stopComponent.cmd ohs1 Stopping System Component ohs1 ... Initializing WebLogic Scripting Tool (WLST) ... Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands Reading domain from F:/OHS/user_projects/domains/base_domain Please enter Node Manager password: Connecting to Node Manager ... Successfully Connected to Node Manager. Killing server ohs1 ... Successfully killed server ohs1 Successfully disconnected from Node Manager. Exiting WebLogic Scripting Tool. Done Step:2   Invoke WLST offline F:\OHS\oracle_common\common\bin>wlst.cmd Initializing WebLogic Scripting Tool (WLST) ... Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands wls:/offline> Step:3 Conne...
1 comment
Read more

Avoid password prompt when using startComponent.sh to start OHS 12c

Step:1 Start Ohs With Password Prompt F:\OHS\user_projects\domains\base_domain\bin>startComponent.cmd ohs1 Starting system Component ohs1 ... Initializing WebLogic Scripting Tool (WLST) ... Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands Reading domain from F:/OHS/user_projects/domains/base_domain Please enter Node Manager password: Connecting to Node Manager ... Successfully Connected to Node Manager. Starting server ohs1 ... Successfully started server ohs1 ... Successfully disconnected from Node Manager. Exiting WebLogic Scripting Tool. Done Step:2 Store the password for avoid ohs password F:\OHS\user_projects\domains\base_domain\bin>startComponent.cmd ohs1 storeUserConfig Starting system Component ohs1 ... Initializing WebLogic Scripting Tool (WLST) ... Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands Reading domain from F:/OHS/u...
Post a Comment
Read more