LO91468: USER WITH MULTIPLE DEVICES WITH DIFFERENT MAIL FILTERS IS MISSING DATA ON THE UNLIMITED FILTERING DEVICE
Direct links to fixes
Closed as program error.
A user had a device with unlimited filter set for mail and only had 30 days of mail. There were multiple devices and one of them had 30 days of mail set as the filter (not unlimited). The unlimited filter device had unlimited data and then the data outside of 30 days disappeared. This was caused by a timing issue between threads in the Traveler server. The one thread started loading the device information. As part of loading the device information, a prime sync was initiated on a separate thread. When the prime sync thread looked for the device preferences, not all of the device information had been loaded yet, so it made the data management decisions based on the available information. In this case, the unlimited device was missing but the 30 day device was present, so the 30 days was used. However, if the device happened to be loaded in the other order and the unlimited device was the one present for the prime sync, there would have been no issue, so it is not simply just having multiple devices with different filters that would cause this issue. Also, if the loading thread finishes loading all the device information before the prime sync thread gets that far, you won't have this issue. This timing issue has been present for many years and is considered rare. This can happen any time a user is loaded on a server: server startup or load balancing from one server to another, for examples.
Timing issue when using multiple devices with different e-mail filters may apply the same filter to both devices.
IBM Traveler server has been updated to resolve this issue.
This fix is included in IBM Traveler 220.127.116.11 and later releases. For the latest IBM Traveler 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: