LO90482: HIGH THREAD COUNTS DUE TO DB CONTENTION ON THE HEARTBEAT PROCESSING
Direct links to fixes
Closed as program error.
High thread counts are seen in Traveler where most of the threads are waiting to update the heartbeat information including the number of users and devices in the TS_GLOBAL table. If the threads are doing work that is controlled OrderLatch's to provide proper operational sequencing, warnings about the latches not being able to be maintained and timing out may also be seen; they timeout because of the contention in the Heartbeat processing. APAR LO89745 (first shipped in 184.108.40.206) prevented the DB connections from getting backlogged because of the contention on the Heartbeat processing, but that pushed the issue back to the threads but still resulted in a backlog in some situations. This APAR should resolve both the DB connection and thread backlogs by making the Heartbeat processing non-blocking.
During startup or when load balancing a large number of users the Traveler server may become constrained on threads and/or DB connections.
The Traveler server was updated to batch heartbeat updates and reduce need for multiple threads and database transactions.
This fix will be included in IBM Traveler 220.127.116.11 and later releases. For the lastest available Traveler Server release see this technote: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
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