tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From BugRat Mail System <tomcat-b...@cortexity.com>
Subject BugRat Report #148 has been filed.
Date Thu, 21 Sep 2000 13:43:43 GMT
Bug report #148 has just been filed.

You can view the report at the following URL:

   <http://znutar.cortexity.com:8888/BugRatViewer/ShowReport/148>

REPORT #148 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 32b4
   JVM Release: Solaris_JDK_1.1.8_10
   Operating System: SunOS
   OS Release: 5.7 Generic_106541-02 sun4u sparc SUNW,Ultra-5_10
   Platform: Solaris

Synopsis: 
No workers found when trying to access jsp or servlet through mod_jk and apache

Description:
This seems to be a serious problem, atleast on my platform
as no jsp/servlet pages can be served through apache while 
expiriencing this condition.

When accessing a jsp page through apache i get the following error in jk.log
[jk_worker.c (123)]: Into wc_get_worker_for_name ajp12
[jk_worker.c (127)]: wc_get_worker_for_name, done did not found a worker

I can access the same .jsp through tomcat when accessing it 
directly. 

When apache is started  "jk_post_config NULL" is written st
stdout. i checked the source and i assume that WAS_BORN_BY_APACHE
is not accessible to mod_jk. This leads to mod_jk being started without any workers initialized.

Mime
View raw message