[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-developers] Tomcat 4.0.4 on RAQ4

At 22.56 25/07/2002 -0700, you wrote:

Sorry for the delay, I stepped out for some entertainment.


Understandable - it's a matter of timezones.



At this point sounds like you need to consult the logs. What is in
Tomcat's logs, and what is in the mod_jk log? I would be curious to see
that.

In catalina_log.txt :
2002-07-26 01:26:00 HttpProcessor[8080][4] Stopping background thread
2002-07-26 01:26:00 HttpProcessor[8080][3] Stopping background thread
2002-07-26 01:26:00 HttpProcessor[8080][2] Stopping background thread
2002-07-26 01:26:00 HttpProcessor[8080][1] Stopping background thread
2002-07-26 01:26:00 HttpProcessor[8080][0] Stopping background thread
2002-07-26 01:26:00 HttpConnector[8080] Stopping background thread
2002-07-26 01:26:00 Ajp13Processor[8009][4] Stopping background thread
2002-07-26 01:26:00 Ajp13Processor[8009][3] Stopping background thread
2002-07-26 01:26:00 Ajp13Processor[8009][2] Stopping background thread
2002-07-26 01:26:00 Ajp13Processor[8009][1] Stopping background thread
2002-07-26 01:26:00 Ajp13Processor[8009][0] Stopping background thread
2002-07-26 01:26:00 Ajp13Connector[8009] Stopping background thread
2002-07-26 01:46:02 HttpConnector Opening server socket on all host IP addresses 
2002-07-26 01:46:35 HttpConnector[8080] Starting background thread
2002-07-26 01:46:35 HttpProcessor[8080][0] Starting background thread
2002-07-26 01:46:35 HttpProcessor[8080][1] Starting background thread
2002-07-26 01:46:35 HttpProcessor[8080][2] Starting background thread
2002-07-26 01:46:35 HttpProcessor[8080][3] Starting background thread
2002-07-26 01:46:35 HttpProcessor[8080][4] Starting background thread
2002-07-26 01:46:35 Ajp13Connector[8009] Opening server socket on all host IP addresses 
2002-07-26 01:46:35 Ajp13Connector[8009] Starting background thread
2002-07-26 01:46:36 Ajp13Processor[8009][0] Starting background thread
2002-07-26 01:46:36 Ajp13Processor[8009][1] Starting background thread
2002-07-26 01:46:36 Ajp13Processor[8009][2] Starting background thread
2002-07-26 01:46:36 Ajp13Processor[8009][3] Starting background thread
2002-07-26 01:46:36 Ajp13Processor[8009][4] Starting background thread
2002-07-26 02:55:06 Ajp13Processor[8009][5] Starting background thread
2002-07-26 02:55:19 Ajp13Processor[8009][6] Starting background thread

The mod_jk.log is very long:
[jk_uri_worker_map.c (156)]: Into jk_uri_worker_map_t::uri_worker_map_alloc
[jk_uri_worker_map.c (196)]: Into jk_uri_worker_map_t::uri_worker_map_open
[jk_uri_worker_map.c (211)]: jk_uri_worker_map_t::uri_worker_map_open, rule map size is 6 [jk_uri_worker_map.c (285)]: Into jk_uri_worker_map_t::uri_worker_map_open, exact rule /examples=ajp13 was added [jk_uri_worker_map.c (267)]: Into jk_uri_worker_map_t::uri_worker_map_open, match rule /examples/=ajp13 was added [jk_uri_worker_map.c (285)]: Into jk_uri_worker_map_t::uri_worker_map_open, exact rule /jk=ajp13 was added [jk_uri_worker_map.c (267)]: Into jk_uri_worker_map_t::uri_worker_map_open, match rule /jk/=ajp13 was added [jk_uri_worker_map.c (285)]: Into jk_uri_worker_map_t::uri_worker_map_open, exact rule /cocoon=ajp13 was added [jk_uri_worker_map.c (267)]: Into jk_uri_worker_map_t::uri_worker_map_open, match rule /cocoon/=ajp13 was added [jk_uri_worker_map.c (296)]: Into jk_uri_worker_map_t::uri_worker_map_open, there are 6 rules 
[jk_uri_worker_map.c (317)]: jk_uri_worker_map_t::uri_worker_map_open, done
[jk_worker.c (82)]: Into wc_open
[jk_worker.c (207)]: Into build_worker_map, creating 2 workers
[jk_worker.c (213)]: build_worker_map, creating worker ajp13
[jk_worker.c (138)]: Into wc_create_worker
[jk_worker.c (152)]: wc_create_worker, about to create instance ajp13 of ajp13
[jk_ajp13_worker.c (711)]: Into ajp23_worker_factory
[jk_worker.c (161)]: wc_create_worker, about to validate and init ajp13
[jk_ajp13_worker.c (386)]: Into jk_worker_t::validate
[jk_ajp13_worker.c (399)]: In jk_worker_t::validate for worker ajp13 contact is localhost:8009 
[jk_ajp13_worker.c (425)]: Into jk_worker_t::init
[jk_worker.c (177)]: wc_create_worker, done
[jk_worker.c (223)]: build_worker_map, removing old ajp13 worker
[jk_worker.c (213)]: build_worker_map, creating worker ajp14
[jk_worker.c (138)]: Into wc_create_worker
[jk_worker.c (148)]: wc_create_worker NULL factory for ajp14
[jk_worker.c (229)]: build_worker_map failed to create workerajp14
[jk_uri_worker_map.c (156)]: Into jk_uri_worker_map_t::uri_worker_map_alloc
[jk_uri_worker_map.c (196)]: Into jk_uri_worker_map_t::uri_worker_map_open
[jk_uri_worker_map.c (211)]: jk_uri_worker_map_t::uri_worker_map_open, rule map size is 6 [jk_uri_worker_map.c (285)]: Into jk_uri_worker_map_t::uri_worker_map_open, exact rule /examples=ajp13 was added [jk_uri_worker_map.c (267)]: Into jk_uri_worker_map_t::uri_worker_map_open, match rule /examples/=ajp13 was added [jk_uri_worker_map.c (285)]: Into jk_uri_worker_map_t::uri_worker_map_open, exact rule /jk=ajp13 was added [jk_uri_worker_map.c (267)]: Into jk_uri_worker_map_t::uri_worker_map_open, match rule /jk/=ajp13 was added [jk_uri_worker_map.c (285)]: Into jk_uri_worker_map_t::uri_worker_map_open, exact rule /cocoon=ajp13 was added [jk_uri_worker_map.c (267)]: Into jk_uri_worker_map_t::uri_worker_map_open, match rule /cocoon/=ajp13 was added [jk_uri_worker_map.c (296)]: Into jk_uri_worker_map_t::uri_worker_map_open, there are 6 rules 
[jk_uri_worker_map.c (317)]: jk_uri_worker_map_t::uri_worker_map_open, done
[jk_worker.c (82)]: Into wc_open
[jk_worker.c (207)]: Into build_worker_map, creating 2 workers
[jk_worker.c (213)]: build_worker_map, creating worker ajp13
[jk_worker.c (138)]: Into wc_create_worker
[jk_worker.c (152)]: wc_create_worker, about to create instance ajp13 of ajp13
[jk_ajp13_worker.c (711)]: Into ajp23_worker_factory
[jk_worker.c (161)]: wc_create_worker, about to validate and init ajp13
[jk_ajp13_worker.c (386)]: Into jk_worker_t::validate
[jk_ajp13_worker.c (399)]: In jk_worker_t::validate for worker ajp13 contact is localhost:8009 
[jk_ajp13_worker.c (425)]: Into jk_worker_t::init
.......................
[jk_uri_worker_map.c (335)]: jk_uri_worker_map_t::uri_worker_map_close, NULL parameter [jk_uri_worker_map.c (185)]: In jk_uri_worker_map_t::uri_worker_map_free, NULL parameters [jk_uri_worker_map.c (335)]: jk_uri_worker_map_t::uri_worker_map_close, NULL parameter [jk_uri_worker_map.c (185)]: In jk_uri_worker_map_t::uri_worker_map_free, NULL parameters [jk_uri_worker_map.c (335)]: jk_uri_worker_map_t::uri_worker_map_close, NULL parameter [jk_uri_worker_map.c (185)]: In jk_uri_worker_map_t::uri_worker_map_free, NULL parameters [jk_uri_worker_map.c (335)]: jk_uri_worker_map_t::uri_worker_map_close, NULL parameter [jk_uri_worker_map.c (185)]: In jk_uri_worker_map_t::uri_worker_map_free, NULL parameters [jk_uri_worker_map.c (335)]: jk_uri_worker_map_t::uri_worker_map_close, NULL parameter [jk_uri_worker_map.c (185)]: In jk_uri_worker_map_t::uri_worker_map_free, NULL parameters [jk_uri_worker_map.c (335)]: jk_uri_worker_map_t::uri_worker_map_close, NULL parameter [jk_uri_worker_map.c (185)]: In jk_uri_worker_map_t::uri_worker_map_free, NULL parameters 

The Tomcat 404 is here, in the localhost_access.log.txt
It looks like it isn't picking up the correct path
213.156.38.106 - - [26/Jul/2002:02:46:59 00] "GET /examples/jsp/num/numguess.jsp?guess=2 HTTP/1.1" 200 580 213.156.38.106 - - [26/Jul/2002:02:47:06 00] "GET /examples/jsp/num/numguess.jsp?guess=34 HTTP/1.1" 200 579 213.156.38.106 - - [26/Jul/2002:02:47:10 00] "GET /examples/jsp/num/numguess.jsp?guess=20 HTTP/1.1" 200 579 
213.156.38.106 - - [26/Jul/2002:02:48:37 00] "GET /test.jsp HTTP/1.1" 404 600
213.156.38.106 - - [26/Jul/2002:02:48:39 00] "GET /test.jsp HTTP/1.1" 404 600


You still have the mod_jk.so on the machine correct?


I backed up the Cobalt version and compiled a new one.



When you say 404, is that from Tomcat or Apache?
The 404 is from Tomcat not Apache - which is very confusing, as the file is there 



Let me know what is in the logs and we can go from there. Sounds very
strange though.


Tell me about it! That's why I'm getting balder :-)


Mr. Michele Neylon
Blacknight Solutions - affordable linux hosting
http://www.blacknightsolutions.com/


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.