LO82214: RED SERVER STATUS FOR ORPHANED LONG RUNNING DS THREAD.
Closed as program error.
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.
Restart the server to clear the thread.
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.
The Notes Traveler server has been updated to avoid this particular scenerio.
This fix is included 184.108.40.206 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
Reported component name
LOTUS NOTES TRA
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels