PK83733: SCHEDULED TASKS ARE NOT RUN WHEN THE WORKTIMEOUT OF THE WORK MANAGER IS SET TO A LOW VALUE.

Fixes are available

APAR status

Closed as program error.

Error description

If a scheduler is defined with work manager settings that have
a worktimeout set, if no tasks are started within the
worktimeout period after the scheduler daemon is started, then
the scheduler daemon is stopped.  This results in no scheduled
tasks being run on that scheduler.
.
   For example, if the work manager settings for the scheduler
are as follows
<factories xmi:type="workmanager:WorkManagerInfo"
xmi:id="WorkManagerInfo_1237990250598"
name="SchedulerWorkManager"
jndiName="ibm/SchedWorkManager" minThreads="1" maxThreads="3"
threadPriority="5" numAlarmThreads="2" isGrowable="false"
workTimeout="3600" workReqQSize="10000" workReqQFullAction="1">
  <serviceNames>security</serviceNames>
  </factories>
.
   The units on workTimeout are in ms.  So, 3600 is 3.6 seconds.
Here is the message that is logged when the scheduler daemon is
started.
.
[3/25/09 11:24:58:554 EDT] 0000001e SchedulerDaem I SCHD0038I:
TheScheduler Daemon for instance sched/IBM has started.
[3/25/09 11:24:58:559 EDT] 0000001e SchedulerDaem 3 Started
daemon for: Scheduler_sched.ibm_D0
.
   There is no indication with a message that the scheduler
daemon stops.  With the Scheduler MustGather trace, you will see
this event 3.6 seconds later, if no scheduled task is run within
the initial workTimeout.
.
  [3/25/09 11:25:02:191 EDT] 0000001d WorkTimeoutLi 3 alarm
<null>
[3/25/09 11:25:02:192 EDT] 0000001d SchedulerDaem > release
Entry
[3/25/09 11:25:02:193 EDT] 0000001d SchedulerDaem < release Exit
[3/25/09 11:25:02:193 EDT] 0000001d WorkTimeoutLi 3 alarm
release AsynchBean work: Scheduler_sched.ibm_D0
[3/25/09 11:25:02:193 EDT] 0000002d SchedulerDaem > stopDaemon
Entry
.
   This prevents later scheduled jobs from being run on that
scheduler, since the SchedulerDaemon is an integral part of that
process.
.
   This is a problem in the WebSphere Application Server
scheduler processing.  The initial timeout should only affect
non-daemon work.

Local fix

Either raise the workTimeout setting to a higher value or remove
the setting.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server who use workmangers with deamon work *
****************************************************************
* PROBLEM DESCRIPTION: Deamon work is timing out stop the      *
*                      workmanager completely                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Only non deamon work should have a time out listener
configured. Currently, work manager time out is being applied
to both deamon and non-deamon work

Problem conclusion

This APAR will ensure that only non-deamon work times out
according to configured work manager time out setting.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.37  6.1.0.27  7.0.0.5  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK83733
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
60S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-31
Closed date
2009-04-08
Last modified date
2009-04-08

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK83733: SCHEDULED TASKS ARE NOT RUN WHEN THE WORKTIMEOUT OF THE WORK MANAGER IS SET TO A LOW VALUE.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?