Hi Pavel
Unfortunatelly it is comming over ssl. But while testing directly
with soapUI it always returned correctly and no errors or incomplete
responses occured.
Set the " -Djavax.net/debug=all" system property when you start
Synapse, and check the log, or share it with me. This will contain
the full message when decrypted from the SSL session
Thanks.
I set it (logs attached).
There is clearly visible that no whole message is received through ssl
transport. But now I don't understand what causes it - remote server
is closed the connection before data are sent or Synapse closes
connection too early?
Hmm.. this is interesting..
2008-06-25 14:32:46,934 [192.168.0.50-PAVEL3] [I/O dispatcher 1] DEBUG
ClientHandler HTTP connection [closed]: Input ready
2008-06-25 14:32:46,934 [192.168.0.50-PAVEL3] [I/O dispatcher 1] DEBUG
ClientHandler HTTP connection [closed]: Content decoder [content length:
7919; pos: 4125; completed: true]
2008-06-25 14:32:46,949 [192.168.0.50-PAVEL3] [I/O dispatcher 1] DEBUG
ClientHandler HTTP connection [closed]: Closed
This could be a bug as well.. but I need to reproduce this to debug
something at this level.. Can you tell me which version of Synapse you
are using?
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
