[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] default response timout

David Robison wrote:
I noticed that the default timeout response was changed from one minute to MAX_INT in release 1.0.7. Was there a reason for this change. We have run into a situation when we issue a subscribe command but never get a response. With the MAX_INT timeout, the program hangs. I was thinking about resetting the response timeout to one minute but wanted to make sure that this would not cause additional problems.

Thanks, David Robison

Why is the response not returning?

client --> subscribe --> xmlBlaster
<--- subscribeReturnQos <--

is it xmlBlaster which is not responding?
I think the first step is to track down the reason for the missing

We have introduced the MAX_INT mainly for callbacks. If the callback carries
a huge message over a modem (taking for example half a day)
it may cause a ping to be blocked which in turn aborts the transfer and the callback dispatcher goes to polling.
Then it is retried again, fails again and so on.

This situation is not this critical anymore as the current xmlBlaster
detects the bytes transfered and ommits the ping if bytes travel over the socket.

Yes, i would say you can reduce the MAX_INT in your case,


Marcel Ruff