IBM Support

LO90183: VERSE SYNCS ABORTED FOR TOO MANY EMPTY MESSAGES BECAUSE OF SIZING MISMATCHES IN CHUNKED DATA

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • 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.
    

Local fix

  • 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.
    

Problem summary

  • 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.
    

Problem conclusion

  • The IBM Traveler server has been updated to ensure this problem
    does not occur.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO90183

  • Reported component name

    LOTUS NOTES TRA

  • Reported component ID

    5724E6204

  • Reported release

    901

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-09-09

  • Closed date

    2016-11-09

  • Last modified date

    2016-11-09

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    LOTUS NOTES TRA

  • Fixed component ID

    5724E6204

Applicable component levels

  • R901 PSY

       UP



Document information

More support for: IBM Traveler

Software version: 9.0.1

Reference #: LO90183

Modified date: 09 November 2016


Translate this page: