PM85339: Write-behind loaders do not correctly handle the LoaderNotAvailableException exception when the back-end

APAR status

• Closed as program error.

Error description

• Errors occur when the back-end database fails, and a custom
  loader sends the LoaderNotAvailableException exception in a
  WebSphere eXtreme Scale configuration with a write-behind
  loader configuration. The error is externalized to client
  applications as failures during transactions (for example, the
  LoaderNotAvailableException occurs with the message, "Phsyical
  loader is down"), or during replication, or partition
  initialization.
  
  In some cases, this behavior prevents data replication or
  prevents partitions from starting up.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere eXtreme Scale users who create    *
  *                  custom loader plug-ins and use              *
  *                  write-behind loaders.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: TargetNotAvailableException conditions  *
  *                      or data loss occurs when the            *
  *                      LoaderNotAvailableException is thrown   *
  *                      by the loader.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The LoaderNotAvailableException is not handled in all places
  where it might occur. Some actions that happen when the
  LoaderNotAvailableException occurs are handled incorrectly. Log
  messages sre written repeatedly for an already-detected error
  condition and the write-behind loader does not retry in a
  timely way.
  

Problem conclusion

• The LoaderNotAvailableExceptions are handled, logged and the
  retry interval for the data grid changes can be adjusted.
  

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

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels

• R860 PSY

     UP