Hi Eric
This brings me to a new idea and I what like to hear what you think
about.
What if I would decrease the value for http.socket.timeout to 2 for
Synapse, so to be definitely lower than the one on the server side. What
would be the expected result? Would I see another exception, if the
t
Hi Asankha,
thanks for your reply as well! Please see my comments below!
> One thing you could analyze is the TCP socket timeout times in the
> different environments..
Hmm, TCP socket timeout should be the same, but I will investigate.
Also our response times are pretty low. Average of 10-15 ms
Oleg,
thanks a lot for your reply! Please see my comments inline!
> > The problem is I don't understand the cause of this exception. It occurs
> during the read on a Socket-Channel. So I think the server might close the
> connection while the ESB is reading. But maybe internally some kind of
> po
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
On Wed, 2008-06-25 at 18:13 +0200, Hubert, Eric wrote:
> Hi devs!
>
> first of all I'd like to apologize for posting a "user-problem" to two
> dev-lists. I only did this as have not much background knowledge of the NIO
> implementation and think a solid understanding of NIO is necessary to help
Hi devs!
first of all I'd like to apologize for posting a "user-problem" to two
dev-lists. I only did this as have not much background knowledge of the NIO
implementation and think a solid understanding of NIO is necessary to help
tackling our problem.
We are using the WSO2 ESB which is based
