Patrick Ohly wrote: > On Mo, 2011-09-12 at 09:36 +0100, Justas Poderys wrote: >> On Mon, 2011-09-12 at 08:07 +0200, Patrick Ohly wrote: >>> On So, 2011-09-11 at 22:25 +0100, Justas Poderys wrote: >>> Looks like the Funambol Android client is sending a malformed message. >>> There were reports like that a while back; I think the answer in the >>> Funambol forums at that time was that it was only tested with the >>> Funambol server. >>> >>> Can you increase the loglevel to 5 >>> in /home/justas/.config/syncevolution/default/peers/jphtc/config.ini and >>> try again? >> >> I have emailed full trace gziped to your email. > > Sorry, I should have been more explicit: I need the full directory, in > particular the syncevolution-log_msg003_006_incoming.xml message dump. >
Hi Patrick! I had the same problem a while ago but stopped investigating because my time is very limited right now. What I found was that the incoming message 003_006 (mine was numbered the same) contained a full copy of the previous message. That was surprisingly close to the 64k maxMsgSize I had set IIRC. After that followed another <SyncML> tag starting the next message. However, the XML was declared (even by the browser) as not well-formed (or not valid?) because of the repeated top-level tag. Looked to me a bit like the message buffer had not been cleared after reaching the maximum message size. Dunno whether it's a client or server issue. I was using SyncEvolution 1.1.99.5a from Debian unstable and the Android Funambol client 10.0.6. I could not find that specific log directory just now, but I'll try to reproduce it next week or so and send you the log directory for additional reference. Regards, André -- Greetings... From: Andre Colomb <[email protected]>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
