very careful and returns EDEADLOCK even in
>>> situations were you can mathematically prove, that a deadlock is not
>>> possible. This happens in a multi-threaded environment when more than
>>> one mutex is used.
>>>
>>> Apache httpd and mod_jk use such a
On 06.02.2009 20:40, fredk2 wrote:
Do I understand you correctly that when Mr. Orton said to never use pthread
nor posixsem mutex (http://marc.info/?l=apr-dev&m=108720968023158&w=2) that
is now obsolete news and that Solaris perfected pthread mutex support since.
Joe Orton is always very carefu
end the pthread mutex
> for Solaris which doesn't have the problem and seems to be robust
> despite warnings about pthread mutexes in very old versions of Solaris.
>
> We even once had a discussion about changing the default httpd mutex on
> Solaris once, but I think that discussion d
On 06.02.2009 18:13, fredk2 wrote:
I was doing some stress test (with apache ab, 100 users, 100K requests) to
compare an Apache prefork and worker mpm. The test url is a simple hello
servlet on Tomcat 6.0.x via mod_jk. On my Sparc Solaris 10 server with only
the Apache set to worker mpm I see fo
mutex? sysvsme, posixsem, pthread **?
any comment will be appreciated.
Many thanks, Fredk
--
View this message in context:
http://www.nabble.com/Deadlock-situation-detected-avoided-with-jk_log_lock-tp21876381p21876381.html
Sent from the Tomcat - User mailing list archiv
