Apache 2.0.64 using worker/pthreads on Solaris 10 mod_perl-2.0.4 I recently installed a new release of an application developed by another team member. It locked up our apache instances as soon as they came under load.
pstack showed that all the Apache HTTPD server processes have all lwp/threads stuck in modperl_tipool_pop modperl_interp_get modperl_interp_select modperl_response_handler_cgi except one that's stuck in cond_wait_queue cond_wait pthread_cond_wait pthread_cond_wait xmlRMutexLock xmlCatalogCleanup xmlCleanupParser XS_XML__LibXML_END Perl_pp_entersub Perl_call_sv modperl_perl_call_list modperl_perl_call_endav modperl_perl_destruct I'm not a perl programmer. Can someone advise the best way to determine what's going on here? Am I facing some sort of default behaviour of a libxml-dependent perl library where it's placing an unnecessary read mutex and getting in some sort of deadlock? Any advice would be appreciated. Cheers, Ryan
