On 09.11.2009 03:13, Mohit Anchlia wrote:
Thanks. Looks like we are hitting the same bug.
I am still looking for an answer to one of my questions that I posted earlier.
To narrow down I just left one node running and started the test. When I
look at JkStatus worker I see that even though
On 08.11.2009 01:36, Mohit Anchlia wrote:
Could someone please help me understand this?
What about adding connectionTimeout to the JBoss Connector element (and
keep its value in sync with connection_pool_timeout^for the ajp workers.
Note that the Connector attribute is in milliseconds, the
Thanks. Looks like we are hitting the same bug.
I am still looking for an answer to one of my questions that I posted earlier.
To narrow down I just left one node running and started the test. When I
look at JkStatus worker I see that even though all other nodes are down
it's still showing OK in
Mohit Anchlia wrote:
I am looking at the tcpdump but I don't see packet retransmits. What
should I expect to see in tcpdump? thanks for your help.
Mohit,
have you checked that *all* the workers which your configure in
workers.properties really have a corresponding back-end Tomcat ?
Maybe
To narrow down I just left one node running and started test. When I
look at JkStatus worker I see even though all other nodes are down
it's still showing OK in the status. I am not sure why it would do
that. Could this be the reason why I am seeing slow response times in
mod-jk?
On Fri, Nov 6,
Could someone please help me understand this?
On Sat, Nov 7, 2009 at 8:50 AM, Mohit Anchlia mohitanch...@gmail.com wrote:
I am also seeing that in Jboss (Back End) that there are lot of keep
alive sessions and I think that's the reason I am seeing the timeout.
As I add new web server it hits
