PM77948: The TargetNotAvailableException exception occurs when you set the RequestRetryTimeout value to 0 and use COPY_TO_BYTES.

APAR status

• Closed as program error.

Error description

• When you use WebSphere eXtreme Scale V7.1.1 with WebSphere
  Application Server, use the COPY_TO_BYTES copy mode, and
  set the requestRetryTimeout=0 value in the client-side
  property file, you might experience the following error:
  
  com.ibm.websphere.objectgrid.TargetNotAvailableException:
  Retrying therequest expired, the current timeout is set to
  5000 (ms).
  extremeScalePerf:eServiceGrid:eServiceMapSet:0
  at
  com.ibm.ws.objectgrid.client.ORBClientCoreMessageHandler.sendMes
  sage
  (ORBClientCoreMessageHandler.java:709)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere eXtreme Scale who    *
  *                  use the COPY_TO_BYTES function with a       *
  *                  requestRetryTimeout set to 0                *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using the COPY_TO_BYTES copy       *
  *                      mode,                                   *
  *                      the first request after an initial      *
  *                      connection or after restart of the      *
  *                      data grid fails.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When first connecting to a data grid or after restarting a
  data grid while leaving the client running, a client does meta
  data recovery for the COPY_TO_BYTES function.  When doing this
  recovery, a reply from the server is sent with the updated meta
  data information.  This interaction with the
  server was not taken into consideration when determining
  whether a retry should occur when fail fast is enabled
  (requestRetryTimeout=0).  This APAR allows for an additional
  interaction with the server when doing this recovery logic and
  not does not allow failing fast for this special response type.
  

Problem conclusion

• An interim fix is available for this problem.
  

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

• R711 PSY

     UP

• R850 PSY

     UP

• R860 PSY

     UP