[Tickets #4464] Alert 222 NEXT MESSAGE in SyncML

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=4464
-----------------------------------------------------------------------
 Ticket             | 4464
 Updated By         | alex.masidlover at axiomtech.co.uk
 Summary            | Alert 222 NEXT MESSAGE in SyncML
 Queue              | SyncML
 Type               | Enhancement
 State              | Assigned
 Priority           | 1. Low
 Owners             | Karsten Fourmont
+New Attachment     | syncml_12.xml
-----------------------------------------------------------------------


alex.masidlover at axiomtech.co.uk (2006-09-29 05:04) wrote:

Have tested against m600i - first attempt failed. Server produced its first
full data response and sent it, phone then didn't respond - I've had this
happen with my hacked fix and I think it might be the m600i rather than
horde...

The last log lines from the server are:

Sep 29 12:47:23 HORDE [debug] [horde] SyncML: add:
20060809T174831Z-5148-1001-1-1 at enoch [on line 268 of
"/usr/share/php/SyncML/Sync.php"]
Sep 29 12:47:23 HORDE [debug] [horde] SyncML: max message size reached
cursize=6731 [on line 281 of "/usr/share/php/SyncML/Sync.php"]
Sep 29 12:47:23 HORDE [debug] [horde] SyncML: SyncML: return message
completed [on line 377 of "/usr/share/php/SyncML.php"]

I've also attached the last packet from each of the server and client
(accidentally deleted the wbxml unfortunately - only had the raw XML) and
a packet from the middle of a succesful session.

However the second attempt worked perfectly - many thanks.

Unfortunately the phone is packed up to be returned (I unpacked it for the
tests) however I plan on ordering myself a sim free one in a few weeks so
will be using it daily when that happens and will report if the first
issue recurrs.