-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bruce,
On 3/7/14, 3:08 PM, Bruce Weertman wrote:
> Chris;
>
>> Just curious: why do you have maxKeepAliveRequests=1? That's...
>> not terribly efficient.
>
> That’s a good question and perhaps we should revisit it. I’m a
> little fuzzy on the reas
Chris;
> Just curious: why do you have maxKeepAliveRequests=1? That's... not
> terribly efficient.
That’s a good question and perhaps we should revisit it.
I’m a little fuzzy on the reasoning (it was a while ago that we did this),
but I believe it was so that we would have a more even distributio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bruce,
On 3/6/14, 3:19 PM, Bruce Weertman wrote:
> Thanks for the replies. Here’s some more info.
>> Bruce,
>>
>> On 3/5/14, 1:11 PM, Bruce Weertman wrote:
>>> We have a load balancer talking with tomcat’s running on
>>> multiple backend tomcat ser
Thanks for the replies. Here’s some more info.
> Bruce,
>
> On 3/5/14, 1:11 PM, Bruce Weertman wrote:
>> We have a load balancer talking with tomcat’s running on multiple
>> backend tomcat servers. The tomcats are running web service
>> applications. In doing testing, and as reported by custome
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bruce,
On 3/5/14, 1:11 PM, Bruce Weertman wrote:
We have a load balancer talking with tomcat’s running on multiple
backend tomcat servers. The tomcats are running web service
applications. In doing testing, and as repo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bruce,
On 3/5/14, 1:11 PM, Bruce Weertman wrote:
> We have a load balancer talking with tomcat’s running on multiple
> backend tomcat servers. The tomcats are running web service
> applications. In doing testing, and as reported by customers, we
