I saw that trail... hence some of the questions: - why the error in particular with mod_jk (Rainer wrote once that jk module use pthreads - is that different from other module)? are a few of these errors actually really bad? - is sysvsem a better Mutex to change to on newer Solaris 10 (hasn't the sysvsem configuration been drastically improved since Solaris 8 aka 2004 - eg. no /etc/systems entry required anymore). - Eric Covener wrote: > > On Thu, Jan 15, 2009 at 2:46 PM, fredk2 <fredk2@xxxxxxxxx> wrote: >> >> Hi, >> >> 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 Solaris 10 server with only the >> Apache with worker mpm I see following error messages in my jk log: >> >> Apache/2.2.11 (Unix) with mod_jk/1.2.26 on Solaris 10. >> >> . . . >> [Thu Jan 08 11:42:28 2009] [error] (45)Deadlock situation >> detected/avoided: >> apr_global_mutex_lock(jk_log_lock) failed > > http://markmail.org/message/dedqpmrrkpa224ns > > > -- > Eric Covener > covener@xxxxxxxxx > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > -- View this message in context: http://www.nabble.com/Deadlocks-with-Apache-mpm-worker-and-mod_jk-tp21485344p21486050.html Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|