Set up Work Manager Shutdown Trigger in WebLogic Server 10.3.4 Using WLST
- by adejuanc
WebLogic Server's Work Managers provide a way to control work and
allocated threads. You can set different scheduling guidelines for
different applications, depending on your requirements.
There is a default self-tuning Work Manager, but you might want to
set up a custom work manager in some circumstances: for example,
when you want the server to prioritize one application over another
when a response time goal is required, or
when a minimum thread constraint is needed to avoid deadlock.
The Work Manager Shutdown Trigger is a tool to help with stuck threads in which will do the following:
Shut down the Work Manager.
Move the application to Admin State (not active).
Change the Server instance health state to failed.
Example of a Shutdown Trigger set on the config.xml for your domain:
<work-manager>
<name>stuckthread_workmanager</name>
<work-manager-shutdown-trigger>
<max-stuck-thread-time>30</max-stuck-thread-time>
<stuck-thread-count>2</stuck-thread-count>
</work-manager-shutdown-trigger>
</work-manager>
Understand that any misconfiguration on the Work Manager can lead to
poor performance on the server. Any changes must be done and tested
before going to production.
How can one create a WorkManagerShutdownTrigger for WLS 10.3.4 using WLST?
You should be able to create a WorkManagerShutdownTrigger using WLST by following these steps:
edit()
startEdit()
cd('/SelfTuning/mydomain/WorkManagers')
create('myWM','WorkManager')
cd('myWM/WorkManagerShutdownTrigger')
create('myWMst','WorkManagerShutdownTrigger')
cd('myWMst')
ls()
