IZ76336: UA METAFILE CLIENT MAY FAILED TO RETRIEVE ENTIRE METAFILE

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)
IBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006)

APAR status

• Closed as program error.

Error description

• *************************** APAR Template
  *****************************
  
  Please open an apar with the following severity and information:
  Severity: 3
  Approver:BEH
  Compid:  5724K1000 Tivoli Universal Agent
  Abstract:UA Metafile Client may failed to retrieve entire
  metafile
  
  
  Customer is encountering a socket level communication problem
  between the two machines; th socket error 10035 is occurring on
  UA Metafile Server Client UA, on host gb02qas631o2t27.
  Unfortunately, the encounter with error 10035 is simply due to
  timing of data flow between the Metafile Server machine and the
  Metafile Client machine.  Why this occurs in customer's
  enviroment and not in my test environment is difficult to
  pinpoint, however it is rooted somewhere in either their
  network, their TCP stack, etc.
  
  
  Error 10035 on Windows is ==>
  
  ~~~~~~~~~~~~~~~~~~~~~~
  WSAEWOULDBLOCK 10035
  
  
  Resource temporarily unavailable.
  
  This error is returned from operations on nonblocking sockets
  that cannot be completed immediately, for example recv when no
  data is queued to be read from the socket. It is a nonfatal
  error, and the operation should be retried later. It is normal
  for WSAEWOULDBLOCK to be reported as the result from calling
  connect on a nonblocking SOCK_STREAM socket, since some time
  must elapse for the connection to be established.
  ~~~~~~~~~~~~~~~~~~~~~
  The 10035 error is a non-fatal status and UA is treating it as
  a fatal error, thus UA exits the socket 'read' loop in the
  Metafile Client UA.
  
  Detailed Recreation Procedure:
  
  can't recreate
   Related logs - on ECUREP
  
  ************************ End of APAR Template
  *************************
  

Local fix

• na
  

Problem summary

• UA METAFILE CLIENT MAY FAILED TO RETRIEVE ENTIRE METAFILE
  
  This error is returned from operations on nonblocking sockets
  that cannot be completed immediately, for example 'recv' when no
  data is queued to be read from the socket.  It is a nonfatal
  error, and the operation should be retried later.  It is normal
  for WSAEWOULDBLOCK ( or EWOULDBLOCK) to be reported as the
  result from calling connect on a nonblocking SOCK_STREAM socket,
  since some time must elapse for the connection to be
  established.
  
  So the APAR is not induced by a defect in UA, rather UA is
  missing any retry effort to respond to occurrence of a 'socket
  would block' condition on a non-blocking socket connections.
  The 'socket would block' error is a non-fatal status and UA is
  treating it as a fatal error, thus UA exits the socket 'read'
  loop in the Metafile Client UA.
  

Problem conclusion

• Added 'retry' logic around "socket read" call that will
  repeatedly pause a tenth of a second and then retry the "socket
  read" in event of a 'socket would block' error.  This retry will
  repeat for a maximum of 4 seconds; if the 'socket would block'
  condition still persist then UA has no choice but to abort the
  'socket read' effort.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.1-TIV-ITM-FP0004
    | fix pack | 6.2.2-TIV-ITM-FP0004
  

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

  UNIVERSAL AGENT

• Fixed component ID

  5724K1000

Applicable component levels

• R621 PSY

     UP