Pavel
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?
Going through the code, the only way the LengthDelimitedDecoder could
have set its completed flag to true is if the pos > = content length, or
bytes read was -1.. and this clearly shows that it encountered the end
of stream..
Does this happen with your SOAP UI? Can you get the same SSL log with
it? Also whats the server software that is replying? Its funny that it
doesn't send that header.. but its almost certain that the fault is on
that side... since you are using the synapse demo certificate, did it
some module prematurely terminate the connection?
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
