Re: Deadlock situation detected/avoided with jk_log_lock

2009-02-11 Thread fredk2
Many thanks for your detailed reply. I looked further at the bug numbers you posted... a couple seem significant and happen to be patched on my test server (137111-07). In a couple of my test runs with "AcceptMutex pthread" trailed the tests with sysvsem, but not conclusively. However, contrary t

Re: Deadlock situation detected/avoided with jk_log_lock

2009-02-07 Thread Rainer Jung
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

Re: Deadlock situation detected/avoided with jk_log_lock

2009-02-06 Thread fredk2
Thanks Rainer, 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. You mention that mod_jk uses pthread is that the sam

Re: Deadlock situation detected/avoided with jk_log_lock

2009-02-06 Thread Rainer Jung
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