PM98060: WHEN SUBSCRIBER FETCHES ITEMS FROM SYNDICATOR IT CAN WAIT INDEFI NITELY FOR A REPLY

APAR status

• Closed as program error.

Error description

• During Syndication when the Subscriber contacts the Syndicator
  (through the Item Dispatcher) to fetch items, if that request
  never completes then the Subscriber syndication thread will
  wait
  indefinitely, which causes it to consume threads overtime. This
  defect is to document adding some timeouts to the item
  retrieval
  process.
  
  Opened for release 8001
  

Local fix

• None, other than restart the subscriber
  

Problem summary

• During Syndication when the Subscriber contacts the Syndicator
  (through the Item Dispatcher) to fetch items, if that request
  never completes then the Subscriber syndication thread will
  wait
  indefinitely, which causes it to consume threads overtime. This
  defect is to document adding some timeouts to the item
  retrieval
  process.
  
  Opened for release 8001
  

Problem conclusion

• Analysis: As above
  
  Solution: Two different configurable timeouts have been added:
  1. A 'connection' timeout (deployment.itemDispatcher
  .connectionTimeout, specified in milliseconds) that specifies
  how long to wait before abandoning an attempt to contact the
  Syndicator. Defaults to 1 minute
  2. A 'read' timeout (deployment.itemDispatcher.readTimeout,
  specified in milliseconds) that specifies how long to wait
  before abandoning reading data from the Syndicator. Defaults to
  4 minutes
  
  Additionally a configurable retry limit
  (deployment.itemDispatcher.timeoutRetries) has been added that
  specifies how many times to retry an individual item. Defaults
  to 1 retry
  
  Note 1: Given the nature of the problem being handled (the
  subscriber timing out trying to contact the Syndicator), what
  you will see in the UI when this condition occurs will be
  different between the Syndicator and Subscriber. The Syndicator
  will report a 'Terminated with Confirmation' error and won't
  list a failure within its failed items list (as there was no way
  to inform the Syndicator of the failure) whereas the Subscriber
  will report a 'Update timed out' error.
  Note 2: The failed items will be retried automatically in the
  next Syndication
  

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

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R700 PSY

     UP

• R800 PSY

     UP