LO93196: WP/BB SYNC W/ HEARTBEATINTERVAL CAUSING "DID NOT RESPOND" INFO MESSAGES
Direct links to fixes
Closed as program error.
If a device is using Exchange ActiveSync and using the Sync with HeartbeatInterval for push instead of Ping (this is known to be Windows Phone and BlackBerry devices and not Apple iOS) AND there is new data after 4 minutes but before the HeartbeatInterval minutes, the new data will be delayed to the next sync (either a manual sync or when the HeartbeatInterval expires) and a " IBM Traveler task did not respond within the allotted time frame" INFO messages in the Domino console. This is only applicable to Traveler 22.214.171.124 as the check that is ignoring the request as outdated was modified in 126.96.36.199 in a manner that exposes this timing hole. There is no data loss as the next sync (no matter what causes the sync to happen) will get the data item that otherwise would have been pushed.
ActiveSync HeartbeatInterval used by some devices may result in "Traveler did not respond" messages in the console log.
The IBM Traveler server has been updated to handle this scenario correctly.
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