PI46747: Batch status of an instance is in STARTING when instance state i s FAILED

8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16

APAR status

• Closed as program error.

Error description

• The batchManager commandline could show a result that has
  batch status of STARTING and instance state is FAILED when
  there is an error either on the dispatcher or the executor.
  An example of the output is:
  [2015/08/04 09:48:05.249 -0400] CWWKY0106I:
  JobInstance:{"jobName":"(NOT
  SET)","instanceId":3501,"appName":"BonusPayout#BonusPayout.w
  ar","submitter":"bob","batchStatus":"STARTING","jobXMLName":
  "BonusPayoutJob","instanceState":"FAILED"}
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile- Batch               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Batch status of an instance is in       *
  *                      STARTING when instance state is FAILED  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The batchManager commandline could show the result that has
  batch status of STARTING and instance state is FAILED when there
  is an error either on the dispatcher or the executor.  An
  example of the output is:
   [2015/08/04 09:48:05.249 -0400] CWWKY0106I:
  JobInstance:{"jobName":"(NOT
  SET)","instanceId":3501,"appName":"BonusPayout#BonusPayout.war",
  "submitter":"bob","batchStatus":"STARTING","jobXMLName":"BonusPa
  youtJob","instanceState":"FAILED"}
  

Problem conclusion

• The batch runtime has been updated to set the batch status to
  FAILED to be consistent with the instance state.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.7.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• No work around
  

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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP