On Mon, 2009-10-12 at 13:58 +0100, Andrzej WÄ…sowski wrote:
I can now confirm that (when it appears) I get a message of length
zero saved
with log (synclib_linux_msg001_003_incoming_ERR_0x0010.xml).
I'm pretty confident that this is what is sent by the server. Is there a
chance to debug this from the server side? With nothing sent back to us
it is kind of hard to diagnose what the problem might be.
And there are two outgoing messages stored in the cache too (I attach
both).
Unfortunately both of them are still in SyncML 1.2
That <defaultsyncmlversion> doesn't have the intended effect is worth
investigating, but I think this whole SyncML 1.1 aspect is a red
herring. According to Lukas, Oracle has supported 1.2 for several years
now.
> What was the log level again that you are using? If you use
something
> sufficiently large (try 10), then you should get message dumps of the
> raw message. This is in addition to the "trm*.xml" files that are
> generated while libsynthesis parses the message.
Hmm. I cannot see them in the log (I tried with 30) but perhaps I do not know
where to search. It is attached.
The _ERR_ file is what I was looking for. Seems it is only written when
raw message dumping is enabled (= higher log level). It might be
worthwhile to dump it also at lower levels.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.