tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cost...@covalent.net
Subject Re: mod_jk 4.03 deadlock
Date Thu, 06 Jun 2002 01:25:28 GMT
Hi, 

I found the problem, it seems the lock/unlock were in the wrong order.

Please checkout from head and try again, and let me know if it still
fails.

( thanks for reporting it )

Costin

On 5 Jun 2002, Jean-Francois Nadeau wrote:

> Hi.
> 
> I started to load / stress test our web application. It is running under
> Apache 1.3.22 and Tomcat 4.03 and the mod_jk binary that came with it.
> The OS is Linux 2.4.7, RedHat 7.2 without any updates.
> 
> I discovered that httpd processes deadlock after a certain amount of
> huge requests.
> 
> I decided to investigate the issue by looking at the source code. The
> jk_handler function does not terminate. In fact, the call to
> end->done($end, l) (just before the jk_close_pool) deadlock (not always
> however). That function calls pthread mutex lock/unlock for connection
> reuse.
> 
> I tried to comment all connection reuse code. (in jk_ajp_done,
> jk_ajp_service, jk_ajp_getendpoint). The deadlock is not gone, but it
> appears later.
> 
> Have you ever encountered this problem before? I'd like to fix it. May
> it be a kernel bug, glibc bug? (The problem seems to come from pthread
> mutexes...)
> 
> Thanks a lot,
> 
> jeff
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>
> 
> 


--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message