APAR status
Closed as program error.
Error description
This AND Future and This AND Previous notices currently contain all the affected instances which can be larger than Android client can handle. Changing to only send 1 instance in this case. Android does not need all the instances since it currently does not ghost the notice changes to the calendar.
Local fix
Problem summary
Customer reported that they were unable to complete an initial sync with an Android device. They continually recieved process com.lotus.sync.travellor stopped unexpectedly message on the Android device.
Problem conclusion
The problem was determined to be that the server was sending a Calendar entry that was too large for the device to handle. The device was reporting the max calendar entry size, but the server could potentially send an event that was too large. The lotus Traveler server was updated to honor the max calendar entry size limit.
Temporary fix
This fix will be included in Lotus Traveler 8.5.3.2 and later releases. See this technote for the latest Lotus Traveler maintenance information. http://www.ibm.com/support/docview.wss?uid=swg24019529
Comments
APAR Information
APAR number
LO66243
Reported component name
LOTUS NOTES TRA
Reported component ID
5724E6204
Reported release
853
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-22
Closed date
2012-02-26
Last modified date
2012-02-26
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
R853 PSY
UP
[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSYRPW","label":"Lotus Notes Traveler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.3","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
26 February 2012