LO89840: VERSE SYNCS TO RETRIEVE TRUNCATED MAIL BODIES FAILS IF THE RESPONSE CANNOT BE CONTAINED IN A SINGLE HTTP MESSAGE
Direct links to fixes
Closed as program error.
When the Verse client (Android or iOS) is set to truncate the body of the mail messages and then the user attempts to download the previously truncated message, the sync may get stuck trying to download that message if the retrieved response needs to be split across multiple HTTP messages per the SyncML specification. This may happen with a single mail that is over the maximum message size (for example, on Android this is ~120K). This may also happen if multiple downloads are done at the same time with the last included response, but as long as the last response would fit in a single message by itself, the syncs will eventually complete as the next sync will retry and get just that one in the single message. The problem is that when the client (correctly) asks for the additional messages, the server responds with no additional data. The server should be responding with the next maximum message size worth of data in each message. This continues until the server detects that too many effectively empty messages have been exchanged with the device, logs a message (Traveler: WARNING <username> Client has sent 11 effectively empty messages and the server has nothing pending, so this sync will be stopped to avoid infinite sync loops), and stops the sync to avoid an infinite sync. As long as the client keeps requesting to download this message that is failing, the sync will be stuck and no new mail data will get synced to the device.
1. Delete the mail or move the mail to a non-syncing folder (in Notes or some other client that isn't the mobile client having the sync issue) and reset the device (on the server). 2. Change the client settings to not truncate the body of the mails (attachment settings don't apply) and reset the device (on the server).
May be unable to download entire message on IBM Verse mobile client if the message is very large.
The IBM Traveler server has been updated to correctly handle this scenario.
This fix will be included in IBM Traveler server 126.96.36.199 and all later releases. See this technote for the latest available maintenance release: 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