Hi all, unfortunately decreasing the synapse (nhttp) socket timeout to 25000 ms did not change anything to the current situation. I'm also thinking about what may be the difference between Hessain and SOAP in this regard. Reading RFC 2068 Appendix 19.7: "However, a persistent connection with an HTTP/1.0 client cannot make use of the chunked transfer-coding, and therefore MUST use a Content-Length for marking the ending boundary of each message" a new idea came to my mind. Could this exception also occure if the server closes the connection before reading the whole request? What if the content length would be wrong for some reason? So maybe it would be too small just for certain messages (depending on the binary content)? Could this cause the same exception? If so, how do you calculate the content length? Regards, Eric PS: Sorry for the wild guesses. I have no idea how to further analyze the issue. Any help is greatly appreciated.
________________________________
I think this is a good idea.. as we will close the session on
our own
without an exception, and then BEA can close it from that side
Ok, then I will go ahead and try this out. Is there a way to check
whether this property has been applied properly by Synapse? Some
JMX-monitoring possibility or so?
Unfortunately no.. not unless you set the
org.apache.synapse.transport.nhttp.NHttpConfiguration log level to debug, in
which case you will see something like ""Using nhttp tuning parameter : ..." at
startup. You will need to restart the system for changes to take effect
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org <http://wso2.org/>
http://esbmagic.blogspot.com <http://esbmagic.blogspot.com/>
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
