Eric
Since then we hadn't seen this exception again. But now switching to another
environment we see this exception again, but only for Hessian services.
I have no clue what else could cause this exception. How can we detect the
cause? How to narrow down possible causes, if there are different
possibilities. I don't expect any network outages to be the reason, as other
services (SOAP)-based are working pretty well.
One thing you could analyze is the TCP socket timeout times in the
different environments.. If you drop a file with the name
"nhttp.properties" into the ESB classpath, and add the following line
into it, you can change the Synapse socket timeout
"http.socket.timeout=60000" <- this is in ms. Maybe you can do a similar
thing with the BEA server..
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
