Hi,

first 1.2.10 is very ancient. You should upgrade to 1.2.20.

To free (close) connections between apache and tomcat you can then use
the attribute connection_pool_timeout (see documentation of 1.2.20). To
make the connections more robust, you can also use connect_timeout and
prepost_timeout.

Errno 54 on most platforms is "Connection reset by peer", although I'm
not sure about Win 2K3. I don't know exactly how 1.2.10 behaves, but
maybe this was because the remote (=Tomcat) side of the connection had
an idle timeout, but mod_jk not. If that was the reason, this message
should not have a noticable consequence to the users.

There is no memory "leak" known for mod_jk. Most people secure Apache
against leaks by setting MaxRequestsPerChild to an appropriate value.

If you've still got problems after upgrading, you would need to post
relevant parts of your workers.properties, Jk* from apache config and
the connector config.

Note, that info messages really are info, warns or errors are the ones
to look out for (I saw that you had errors for 1.2.10). The info
messages then might help to explain, why warns or errors happened.

Regards,

Rainer

JNeuhoff wrote:
> We are running an Apache 2.0.54 , mod_jk 1.2.10 and Tomcat 5.5.17 on a
> Windows 2003 server box, average web traffic to Tomcat is about 10 to 20
> concurrent HTTP sessions (idle session timeout 15 minutes). After a weekend
> of sudden heavy web traffic with up to 150 simultaneous HTTP sessions we
> experienced 2 server crashes within 24 hours.
>
>
> Even though our Tomcat only ever used 20% of its assigned maximum 512MB JRE
> Memory and never crashed, mod_jk produced loads of error messages along the
> lines:
>
> <<<
> [Sun Jan 14 21:25:37 2007] [info] jk_handler::mod_jk.c (1975): Service
> error=0 for worker=ajp13
> [Sun Jan 14 21:25:40 2007] [error]
> ajp_connection_tcp_send_message::jk_ajp_common.c (918): sendfull
> returned -54 with errno=54
> [Sun Jan 14 21:25:40 2007] [info] ajp_send_request::jk_ajp_common.c
> (1220): Error sending request on a fresh connection
> [Sun Jan 14 21:25:40 2007] [info] ajp_service::jk_ajp_common.c (1724):
> Sending request to tomcat failed, recoverable operation attempt=1
> [Sun Jan 14 21:25:40 2007] [error]
> ajp_connection_tcp_send_message::jk_ajp_common.c (918): sendfull
> returned -54 with errno=54
> [Sun Jan 14 21:25:40 2007] [info] ajp_send_request::jk_ajp_common.c
> (1220): Error sending request on a fresh connection
> [Sun Jan 14 21:25:40 2007] [info] ajp_service::jk_ajp_common.c (1724):
> Sending request to tomcat failed, recoverable operation attempt=2
> [Sun Jan 14 21:25:40 2007] [error]
> ajp_connection_tcp_send_message::jk_ajp_common.c (918): sendfull
> returned -54 with errno=54
> [Sun Jan 14 21:25:40 2007] [info] ajp_send_request::jk_ajp_common.c
> (1220): Error sending request on a fresh connection
> [Sun Jan 14 21:25:40 2007] [info] ajp_service::jk_ajp_common.c (1724):
> Sending request to tomcat failed, recoverable operation attempt=3
> [Sun Jan 14 21:25:40 2007] [error] ajp_service::jk_ajp_common.c (1733):
> Error connecting to tomcat. Tomcat is probably not started or is
> listening on the wrong port. worker=ajp13 failed
>
> I also noticed that one of the 2 Apache.exe processes went up in memory
> usage from 12MB to a 160MB before Apache failed to serve any requests, even
> though both Apche and Tomcat still continued to log incoming requests.
> It seems that mod_jk doesn't release the memory for unused TCP-connection
> sockets involving port 8009 (the one for the ajp13 protocol). Not even a
> restart of the Apache and Tomcat5 NT services cleared up the pipe, they
> still refused to serve requests. So I finally ended up rebooting the whole
> Windows 2003 server box.
>
> Is there a memory leak problem with Apache 2 / mod_jk ? Any help
> appreciated! How can I configure the system to cope with heavier traffic
> and, if necessary, tell the user that the system is too busy and to come
> back later?
>
> In case it's of any importance, here is the relevant workers.properties for
> the ajp13 we are using:
>
> <<<
> # Set properties for worker1 (ajp13)
> worker.ajp13.type=ajp13
> worker.ajp13.host=localhost
> worker.ajp13.port=8009

---------------------------------------------------------------------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)