Diego
You will need to subscribe [1] to this list to post and receive our
replies in future.. I have directly copied you this email this time
We are using a Synapse ESB (1.2) to mediate web service calls to a web
service. In testing, we have an Axis2 client whose requests are sent to
our Synapse ESB which, then forwards the request to the web service. The
web service itself can take a long time (10mins+) to send a response
back. The problem we have is that the client's http connection to the
ESB is closed after 60 seconds and re-tries to send the request up to
four times before giving up.
This is the default behavior of the Axis2 client side, which uses HttpClient
If our client sends the request to the web service directly, the client
happily waits 10mins+ for a response to come back.
Irrespective of the fact that this works or not, I would very strongly
suggest that waiting on a open socket for a synchronous reply for 10
minutes+ does not look like a good approach.. what you should ideally
use is WS-Addressing, and receive the reply on a new channel. With
http/s and real life situations, an http/s connection does not live this
long, and many intermediate nodes may disconnect the connection during
such a long period of inactvity
This leads us to think that we need to configure timeouts within the
Synapse ESB. Is this assumption correct?
Well you can.. even wait for 10 minutes+.. but I would not recommend
this at all..
We tried playing around with the address endpoint's timout durations within
synapse.xml but its not
had any effect on our problem.
Any pointers on this would be greatly appreciated.
You need to drop in a file named nhttp.properties into your classpath
(e.g. lib directory), and adjust the following property as required,
into this file (the value is in milli seconds)
http.socket.timeout=60000
asankha
[1] http://synapse.apache.org/mail-lists.html
