PM23846: UNABLE TO CANCEL SCHEDULER TASKS DUE TO THE TASKINFO FIELD BEING EMPTY

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Scheduler poll daemon fails with a ByteSerializeException
  when it attempts to schedule alarm for the tasks and also the
  application might be unable to cancel the WebSphere Scheduler
  Tasks
  

Local fix

• No Work Around
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server 6.1 and 7.0                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Scheduler poll daemon fails with a      *
  *                      ByteSerializeException                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the scheduler poll daemon attempts to schedule alarms for
  tasks or when the application attempts to cancel tasks the
  scheduler internally needs to access the TASKINFO column of
  the scheduler TASK table. If the scheduler TASK tablespace
  goes full in the Oracle database and if any scheduler tasks
  were
  created at that point, then the rows created in the Scheduler
  TASK table might contain an empty TASKINFO blob data.
  If the TASKINFO blob field is empty then the following
  exception may be seen in the logs when the scheduler attempts
  to access the TASKINFO data.
  com.ibm.ws.scheduler.exception.ByteSerializeException:
  java.io.EOFException
  at
  com.ibm.ws.scheduler.ByteSerializationUtils.getObjectByIDAndVers
  ion(ByteSerializationUtils.java:599)
  at
  com.ibm.ws.scheduler.TaskInfoBinaryData.getObjectByIDAndVersion(
  TaskInfoBinaryData.java:254)
  at
  com.ibm.ws.scheduler.TaskInfoBinaryData.getJ2EEName(TaskInfoBina
  ryData.java:498)
  at
  com.ibm.ws.scheduler.AbstractTask.getJ2EEName(AbstractTask.java:
  1160)
  ..
  ..
  The root cause of the issue was that during the task creation
  if the scheduler tablespace becomes full, scheduler code was
  not
  handling an Oracle database exception and because of this the
  TASKINFO blob may get created with empty values
  java.io.IOException: ORA-01691: unable to extend lob segment
  WPS_BPCDB.SYS_LOB0000063135C00015$$ by 8192 in tablespace
  SCHEDTS
  NOTE: Applying APAR PM23846 only avoids any future occurence of
  the TASKINFO blob getting stored as empty values due to
  scheduler task tablespace going full. However to resolve the
  ByteSerializationException due to scheduler tasks with empty
  TASKINFO blob values, it is necessary to cleanup the corrupt
  tasks from the scheduler task table in consultation with
  support.
  

Problem conclusion

• The scheduler code has been updated to handle the database
  exception appropriately so as to avoid the creation of empty
  TASKINFO blob values.
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.37 and 7.0.0.17.  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 is sysrouted FROM one or more of the following:

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

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP

• R700 PSY

     UP