Wrong "To: " line; sorry about that..
--- Begin Message ---
I'm still using AJP12... I've deployed some SOAP services (SOAP 2.2) and the Tomcat
worker (v 3.2.3 RPMs) that
these requests get mapped to has occasionally locked up and has to be restarted
manually. Could this be a
potential problem for us, even though we're using AJP12? Would the same workaround
potentially solve this?
We're seeing the following in the mod_jk.log:
[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_ajp12_worker.c (601)]: ajpv12_handle_response, error writing back to server
[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_connect.c (143)]: jk_open_socket, connect() failed errno = 111
[jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
[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
etc.
Thanks for any help with this!
Greg Bailey
[EMAIL PROTECTED]
> ------------------------------------------------------------------------
>
> Subject: mod_jk / Ajp13 config fix on heavily loaded system
> Date: Tue, 13 Nov 2001 23:45:22 +0100
> From: GOMEZ Henri <[EMAIL PROTECTED]>
> To: Tomcat Developers List <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
>
> Hi to all,
>
> Some of you may have experienced problems on heavily
> loaded system with mod_jk and Tomcat 3.2/3.3 when using
> ajp13.
>
> As you may know, the Ajp13 connection is permanent
> and is created each time a WebServer task, for
> example an Apache child, have to forward a request
> to Tomcat.
>
> And in Apache server case, the child will stay alive,
> until the client requests load decrease, or when
> a child have passed 1000 requests (MaxRequestsPerChild 1000).
> And till the child close the connection, the Tomcat thread
> stay alive.
>
> By default Apache server support up to 150 childs :
> (MaxClients 150 in httpd.conf)
>
> But by default, the Ajp13 Interceptor won't use more
> than 100 threads, so you're stuck when the 101th Apache
> child want to forward a request and see the following
> infamous trace in mod_jk.log :
>
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (196)]: In
> jk_endpoint_t::connect_to_tomcat, failed errno = 111
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (635)]: Error connecting
> to the Tomcat process.
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (848)]: In
> jk_endpoint_t::service, send_request failed in send loop 2
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (228)]:
> connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (712)]: Error reading
> reply
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (845)]: In
> jk_endpoint_t::service, get_reply failed in send loop 0
> [wed oct 31 11:03:21 2001] [jk_connect.c (143)]: jk_open_socket,
> connect() failed errno = 111
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (196)]: In
> jk_endpoint_t::connect_to_tomcat, failed errno = 111
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (635)]: Error connecting
> to the Tomcat process.
>
> In some case, Apache could be able to connect, since Tomcat listening
> thread will accept incoming connection, but will drop it later if it
> fail to give the socket to a new thread. In that case you'll see
> only in log :
>
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (848)]: In
> jk_endpoint_t::service, send_request failed in send loop 2
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (228)]:
> connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed
> [wed oct 31 11:03:21 2001] [jk_ajp13_worker.c (712)]: Error reading
> reply
>
> Fortunatly, the fix is easy, just configure Ajp13Connector in
> server.xml to support up to 150 threads (or whatever you define
> as MaxClients in Apache, didn't know how on IIS/iPlanet).
>
> <Ajp13Connector port="8009"
> maxThreads="150"
> maxSpareThreads="50"
> minSpareThreads="10" />
>
> Also you should take care of the number of descriptors
> opened in your webapplication, which is :
>
> Tomcat used descriptors (sockets, files)
> + YouWebApp descriptors (files, sockets, jdbc...)
>
> The JVM, like any others process have a limit on the number
> of descriptors it could open (and of course on number of threads).
>
> So take care of closing no more used socket, files and so on.
>
> -
> Henri Gomez ___[_]____
> EMAIL : [EMAIL PROTECTED] (. .)
> PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
> PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>
--- End Message ---
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
