LO90183: VERSE SYNCS ABORTED FOR TOO MANY EMPTY MESSAGES BECAUSE OF SIZING MISMATCHES IN CHUNKED DATA
Direct links to fixes
Closed as program error.
The Android or iOS Verse client syncs don't complete preventing the user from syncing new data while on the server there is this error message: "Client has sent 11 effectively empty messages and the server has nothing pending, so this sync will be stopped to avoid infinite sync loops" There can be many causes of this same symptom with that error message. APAR LO89840 addressed one cause, but this is a different cause as it only arises when the next chunk of data is resized but then the estimate of the resized chunk is still larger than the resized chunk preventing the chunk from ever syncing. When the content is larger than the allowed maximum message size, it must be split across multiple messages. In the process of splitting the content into chunks, the chunk is asked to be no longer than size M. However, that chunk's content must then be encoded in the SyncML message, so the encoded size is estimated as size N. In most cases, N is less than or equal to M and the chunk can be used as-is. The problem for this APAR arises when N is greater than M because the chunk is omitted. On the next message, it does the same calculations, comes to the same conclusion, and the chunk is never included which causes the empty messages and forces the sync to be stopped with the given error message. The fix is to retry the resizing until N is less than or equal to M at which point the chunk can sync and the sync will complete normally. This only applies to clients who are configured to truncate mail bodies (does not include attachments) and are trying to retrieve the full mail bodies. If the client is configured to sync the full mail body initially, then the client cannot hit this issue as they already have the full body and won't try to retrieve it.
The workaround is to set the client to not truncate the body initially as that will avoid having to retrieve the full body later on.
This problem in not common and dependant on the data being encoded. The symptom is inability to download the rest of a truncated message to the IBM Verse client for Android and/or iOS devices.
The IBM Traveler server has been updated to ensure this problem does not occur.
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
Translate this page: