Yes, you said it before Rainer...thanks for your help as always.
Larry
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 28, 2007 12:51 PM
To: Tomcat Developers List
Subject: Re: FW: Delays in mod_jk
Larry Reisler wrote:
> Agreed, the root ca
two seconds.
Larry
-Original Message-
From: jean-frederic clere [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 28, 2007 10:21 AM
To: Tomcat Developers List
Cc: Rainer Jung; Larry Reisler
Subject: Re: FW: Delays in mod_jk
Larry Reisler wrote:
> Rainer --
>
> I recentl
P-366
(http://jira.jboss.org/jira/browse/JBPAPP-366) fixed this too.
I still see the mod_jk architecture as problematic -- it would be better if
cleaning up the sockets would occur on a different thread and without the
critical section locked.
Larry
-Original Message-
From: Larry Re
#x27;t reproduce the behaviour on Linux. Do you use a special
connector for AJP in JBoss, like Tomcats APR connector, or is it just
the plain Coyote connector? Is there a firewall in between httpd and
JBoss? If so, would it be possible to sniff again on both sides?
Larry Reisler wrote:
> I go
andles this request (apart from 1 remaining connection).
If this works for you too, you can sniff the backend traffic after the
ab run and before the final request.
Regards,
Rainer
Larry Reisler schrieb:
> We are running JBOSS 4.21GA(Tomcat 6.0.10) with mod_jk 1.25 on Apache
> 2.2.x, and
e the expired sockets on a queue for later processing by
the maintain thread, or perhaps send the FIN packet and then place them on a
queue.
3. Is there some reason that Tomcat would not be sending the FIN packet to
mod_jk immediately?
Thanks
Larry Reisler
__
