No idea, what's happening, but if you can reproduce very easily, then
you could increase the jk log level to debug or even trace. That way we
will see more precisely, at what point the communication breaks.
You error code 104 on many platforms is "Connection reset by peer". So
there might be additional log information in some jetty log.
Concerning the config (remarks meant for 1.2.25):
> JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
I think that's the default. If you simply delete it, you profit from the
additional logging of milliseconds starting with 1.2.25.
> JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
Only use those, if you know you need them. Don't just copy tghem over
from older configs, even if they used to be recommended.
> workers.properties:
>
> worker.worker1.local_worker=1
Doesn't exist any more. Only useful when used in combination with a load
balancer. Replaced by "distance", but since you don't use a JK load
balancer simply delete it.
> worker.worker1.lbfactor=1
Default value and only useful in combination with a JK load balancer.
> worker.worker1.socket_timeout=500
500 seconds seems to be a relatively high timeout. No problem per se.
Regards,
Rainer
Andrei Neagoe wrote:
Hello,
Until a recent upgrade I've been using Apache2 with Jetty and mod_jk2
just fine. Now, after I upgraded Apache to 2.2.3 and switched to mod_jk
1.2.18 and having the same version of Jetty (4.2.24) I find the
following in the mod_jk.log:
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [error]
ajp_connection_tcp_get_message::jk_ajp_common.c (966): (worker1) can't
receive the response message from tomcat, network problems or tomcat
(127.0.0.1:8019) is down (errno=104)
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [error]
ajp_get_reply::jk_ajp_common.c (1658): (worker1) Tomcat is down or
refused connection. No response has been sent to the client (yet)
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [info]
ajp_service::jk_ajp_common.c (2046): (worker1) receiving from tomcat
failed, recoverable operation attempt=0
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [info]
ajp_service::jk_ajp_common.c (2085): (worker1) sending request to tomcat
failed, recoverable operation attempt=1
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [error]
ajp_connection_tcp_get_message::jk_ajp_common.c (966): (worker1) can't
receive the response message from tomcat, network problems or tomcat
(127.0.0.1:8019) is down (errno=104)
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [error]
ajp_get_reply::jk_ajp_common.c (1658): (worker1) Tomcat is down or
refused connection. No response has been sent to the client (yet)
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [info]
ajp_service::jk_ajp_common.c (2046): (worker1) receiving from tomcat
failed, recoverable operation attempt=1
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [info]
ajp_service::jk_ajp_common.c (2085): (worker1) sending request to tomcat
failed, recoverable operation attempt=2
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [error]
ajp_service::jk_ajp_common.c (2097): (worker1) Connecting to tomcat
failed. Tomcat is probably not started or is listening on the wrong port
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [info] jk_handler::mod_jk.c
(2277): Service error=0 for worker=worker1
Both Apache and Jetty are running on the same box.
mod_jk.conf looks like this:
JkWorkersFile /etc/apache2/workers.properties
JkLogFile /var/log/apache2/mod_jk.log
JkLogLevel info
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
JkShmFile /var/log/apache2/jk.shm
workers.properties:
worker.list=worker1
worker.worker1.port=8019
worker.worker1.host=127.0.0.1
worker.worker1.type=ajp13
worker.worker1.local_worker=1
worker.worker1.retries=2
worker.worker1.lbfactor=1
worker.worker1.socket_timeout=500
worker.worker1.socket_keepalive=1
Server behaviour: everything seems to be working fine except the admin
module of a certain servlet, which gives an http error (don't know
exactly as I don't have access to it) but after 1-2 refreshes workes fine.
I've also tried to switch to latest mod_jk, 1.2.25 (above logs are from
1.2.25) but same thing.
What I can be sure of is that jetty's running just fine, regular
requests are served without ANY problems. I've browsed through a servlet
for at least half an hour and no error. Client feedback also confirms no
weird behavior.
After googleing for a couple of days and trying different
workers.properties settings, I still have no clue on what might be the
cause of those log entries.
Any suggestion is appreciated.
Thanks,
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
