Re: [SyncEvolution] Debugging a connection to Oracle Calendar Server
Patrick,
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).
And there are two outgoing messages stored in the cache too (I attach both).
Unfortunately both of them are still in SyncML 1.2
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.
You mentioned that enabling and disabling WBXML leads to different
results. Can you retry it with both and send us the raw reply of the
server (= *msg*incoming.*)?
They have both zero bytes in both cases. File names are
synclib_linux_msg001_003_incoming_ERR_0x0010.xml
synclib_linux_msg001_003_incoming_ERR_0x2012.wbxml
When you get the 0x2012 error for WBXML, is there anything in the
log
other than the "smlProcessData failed" error?
Not really - it seems pretty much the same otherwise. Nothing that catches
my attention.
Andrzej
Attachments:
- sysynclib_linux_msg001_002_outgoing.xml (application/xml — 9.0 KB)
- sysynclib_linux_trm001_001_outgoing.xml (application/xml — 9.0 KB)
- sysynclib_linux.html (text/html — 117.2 KB)