Title: problem w/ ajp13 - if Tomcat is shutdown
I don't know an answer to this but I have the same problem. If I enable ajp13 with Tomcat 3.2.1, I get lots of connection refused errors if the load increases. ajp12 works fine for me. I saw several posts in this mailing list about this and never saw an answer or something how to fix this.
 
Rainer Kraft
-----Original Message-----
From: Shinta Tjio [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 05, 2001 7:46 PM
To: '[EMAIL PROTECTED]'
Subject: problem w/ ajp13 - if Tomcat is shutdown

I'm having problem with mod_jk if ajp13 is used.

The problem is often reproduced when Tomcat is shut
down without Apache being shut down. When a request
is fired through Apache as soon as Tomcat starts,
I often get Internal Server Error. The mod_jk.log
will have the following:

> [jk_uri_worker_map.c (344)]: Into jk_uri_worker_map_t::map_uri_to_worker
> [jk_uri_worker_map.c (406)]: jk_uri_worker_map_t::map_uri_to_worker,
>   Found a match ajp13
> [jk_worker.c (123)]: Into wc_get_worker_for_name ajp13
> [jk_worker.c (127)]: wc_get_worker_for_name, done  found a worker
> [jk_ajp13_worker.c (651)]: Into jk_worker_t::get_endpoint
> [jk_ajp13_worker.c (536)]: Into jk_endpoint_t::service
> [jk_ajp13.c (346)]: Into ajp13_marshal_into_msgb
> [jk_ajp13.c (480)]: ajp13_marshal_into_msgb - Done
> [jk_ajp13_worker.c (203)]: connection_tcp_get_message: Error -
>    jk_tcp_socket_recvfull failed
> [jk_ajp13_worker.c (619)]: Error reading request
> [jk_ajp13_worker.c (489)]: Into jk_endpoint_t::done

If I hit reload multiple times, eventually Tomcat will
serve the servlet fine.

Did anyone see this problem before? Is there anyway
around this?

shinta

Reply via email to