I did increase the connection timeout from 1 second to 2 seconds. It made no difference. Also, we can't wait for several seconds for a connection. Our legacy system that is driving the messages expects us to return a response fairly quick, so we can't be waiting around for a socket to connect.
I did another load test today which better simulated production traffic. The connections were not remaining persistent all the time. However, we didn't get any connection exceptions either, so I don't know if increasing maxConnections is helping or not. I do know that we have vendors that are complaining because we aren't maintaining persistent connections, so I would really like to make this happen for them if at all possible.
--- On Thu, 2/12/09, Jitendra Kotamraju <Jitendra.Kotamraju_at_Sun.COM> wrote:
From: Jitendra Kotamraju <Jitendra.Kotamraju_at_Sun.COM>
Subject: Re: Major on-line production issue
To: dev_at_jax-ws.dev.java.net
Date: Thursday, February 12, 2009, 10:53 AM
LeRoy Hall wrote:
> Hey Jitu
> I found out that the vendor servers connection timeout is set at 60
seconds.
> We also did a load test last night and found that as long as there is a
constant stream of messages then the same connections are re-used (persistent),
but when the connection goes idle it is closed. Is there anyway to configure
this so that the connections remain open even when they are idle?
>
I don't know any documented networking property to control the idle
timeout. I will find out if JDK team suggests any.
But, do you see a problem with that ? Can you increase the vendor servers
connection timeout and see if that helps(assuming that the vendor changes the
timeout)
thanks,
Jitu
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net