IBM Support

LO81611: SYNC REQUESTS HANDLE OUT OF ORDER COULD CAUSE DEVICE RE-SYNC

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

  • Problem found when reviewing traces from internal test systems.
    Occasionally delays in processing or network delays can result
    in sync messages being recieve out of order.  If this happens
    need to handle better so that the Mobile device does not decide
    to resync all data.
    

Local fix

  • NA
    

Problem summary

  • In some cases sync messages processed out of order can result in
    the device deciding to sync from scratch.  Generally this will
    happen in result to some sort of network delay.
    

Problem conclusion

  • The Notes Traveler server has been update to handle the out of
    order messages in a way that prevents the device from re-syncing
    the data.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO81611

  • Reported component name

    LOTUS NOTES TRA

  • Reported component ID

    5724E6204

  • Reported release

    901

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-08-13

  • Closed date

    2014-09-14

  • Last modified date

    2014-09-14

  • 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

  • R900 PSY

       UP

  • R901 PSY

       UP



Document information

More support for: IBM Traveler

Software version: 9.0.1

Reference #: LO81611

Modified date: 14 September 2014


Translate this page: