LO82214: RED SERVER STATUS FOR ORPHANED LONG RUNNING DS THREAD.

APAR status

• Closed as program error.

Error description

• In an HA environment, if a sync request is received and is in
  between creating the DS thread to process the request and
  starting the DS thread when a second sync request for the same
  sync (same applications, etc.) is received, the DS thread may
  get orphaned.  Eventually, it will be running long enough that
  is causes a Yellow and then Red status message.  There are many
  other reasons why a DS thread could be long running.  This fix
  is only for this particular case which is identified by the Last
  Runnable being never.  If it has ever had a runnable assigned to
  it, that is NOT this issue.
  
  Red status message will look like this:
  
  User xxx on thread Worker-xxx has been running for 215 minutes.
  

Local fix

• Restart the server to clear the thread.
  

Problem summary

• Timing issue in an HA environment could cause a thread to become
  orphaned and eventually show as a long running user thread, when
  its not actually doing anything.
  

Problem conclusion

• The Notes Traveler server has been updated to avoid this
  particular scenerio.
  

Temporary fix

• This fix is included 9.0.0.1 IF8, 9.0.1 IF7 and will be included
  in any future releases.
  
  For the latest available Notes Traveler maintenance releases see
  this article:
  
  http://www.ibm.com/support/docview.wss?uid=swg24019529
  

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 NOTES TRA

• Fixed component ID

  5724E6204

Applicable component levels

• R900 PSY

     UP

• R901 PSY

     UP