PI79520: COMPUTE GRID PROXY JOB ABENDS WITH CC 4084

8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
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
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Proxy job and the Compute Grid job get "out of sync", namely,
  the first job abends whereas the latter ends normally.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5.5                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Compute Grid Scheduler to           *
  *                      Endpoint HTTP dispatch function         *
  *                      attempts to retry dispatching when      *
  *                      encountering certain HTTP error codes.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Compute Grid scheduler to endpoint HTTP dispatch function
  is designed to retry dispatch to an endpoint upon encountering
  most HTTP error codes and not on a small subset of others. In
  the case of network congestion, as denoted by HTTP error
  code -504, the original job dispatch is not guaranteed to have
  been delivered. Currently the dispatch function will attempt
  to retry the dispatch if a HTTP -504 is received from the
  original dispatch attempt. This may lead to a double dispatch
  of the job if the original dispatch was successful but
  hidden by the HTTP -504 return code.
  

Problem conclusion

• Due to unforeseen network conditions and the related HTTP error
  codes that are raised, the Scheduler to Endpoint dispatch path
  should not retry job dispatch on a wider set of network
  congestion related HTTP error codes encountered. The Compute
  Grid Scheduler dispatch path was updated to take into account
  additional network congestion related HTTP error codes upon
  which a dispatch retry should not occur. In its place a new
  warning message, CWLRB6270W, is emitted to indicate network
  congestion is detected and that job dispatch should be
  investigated and potentially manually retried by the operator.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.14.  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

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R800 PSY

     UP