LO93044: PRIME SYNC THREAD EXCESSIVE LOOPING IN FINDCHILDDOCS
Direct links to fixes
Closed as program error.
When processing prime sync for an Event with a large number of slave documents (repeating instances, or replication conflicts, or repair documents, ...), it may loop over all the slave documents multiple times. In extreme cases (for example, 40000 slave documents) this looping can take a very long time, since each slave document must be opened to determine what processing must be done on it. You can see the looping by enabling FINEST logging for the user whose sync is taking longest, and looking in the NTSActivity log for messages with 'findChildDocs'. This fix changes the logic to minimize the looping, so each slave is opened only once, allowing the prime sync to complete much more quickly.
You can ban the master Event document (by UNID) to prevent Traveler from starting the looping.
This is a rare scenario, was discovered by a customer that had 40,000 exception documents to a ToDo entry. This uncovered a performance issue processing that many documents.
The IBM Traveler server has been updated and now processes large events more efficiently.
This fix will be included in the IBM Traveler 188.8.131.52 maintenance release as well as any future releases. For the latest available IBM Traveler Server maintenance 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
Translate this page: