Aha. And the other symptom should have changed too: as long as the
messages are only info level messages, I would not expect any observable
problem about application usage (requests not getting responses, "tomcat
hangs" etc.).
Is that correct? If you still observe problems (apart from the info
level messages): what kind of problems?
Concerning the messages: Most likely either tomcat or a system in
between closed a connection, that was used for a previous request and
kept open by mod_jk for using it again. Depending on your configuration
this is normal. E.g. if you have a connection timeout on the tomcat side
which is much smaller than the connection pool timeout on the mod_jk
side, or if a firewall in between silently drops a connection after a
long time of inactivity.
Regards,
Rainer
mast wrote:
it seem i still get the problem but the message has changed with the new
version :
[Wed Nov 22 05:52:08 2006] [85519:0000] [info]
ajp_send_request::jk_ajp_common.c (1170): (ajp13) socket 40 is not
connected any more (errno=35)
[Wed Nov 22 05:52:08 2006] [85519:0000] [info]
ajp_send_request::jk_ajp_common.c (1194): (ajp13) error sending request.
Will try another pooled connection
[Wed Nov 22 05:52:08 2006] [85519:0000] [info]
ajp_send_request::jk_ajp_common.c (1218): (ajp13) all endpoints are
disconnected or dead
[Wed Nov 22 05:52:08 2006] [85519:0000] [info]
ajp_service::jk_ajp_common.c (1867): (ajp13) sending request to tomcat
failed, recoverable operation attempt=1
----- Original Message ----- From: "Rainer Jung"
<[EMAIL PROTECTED]>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Tuesday, November 21, 2006 8:24 PM
Subject: Re: tomcat stop working for some minute regulary
Thanks for the info.
I would suggest:
Increase JkLogLevel to info. This will most likely give us some more
information about what's happening. Don't use multiple JkLogLevel
directives with different values, as you do at the moment.
If it is possible for you, also update to mod_jk 1.2.19.
Check what happens, if you increase your socket_timeout.
... and finally: there is a protocol named ajp14 that was never
finished. It's somehow misleading to name an ajp13 worker ajp14 :)
mast schrieb:
there is nothing else on the log except many msg like that :
[Tue Nov 21 17:40:41 2006] [error] ajp_service::jk_ajp_common.c (1758):
Error connecting to tomcat. Tomcat is probably not started or is liste
ning on the wrong port. worker=ajp14 failed
[Tue Nov 21 17:41:10 2006] [error] ajp_service::jk_ajp_common.c (1758):
Error connecting to tomcat. Tomcat is probably not started or is liste
ning on the wrong port. worker=ajp14 failed
[Tue Nov 21 17:41:14 2006] [error] ajp_service::jk_ajp_common.c (1758):
Error connecting to tomcat. Tomcat is probably not started or is liste
ning on the wrong port. worker=ajp14 failed
[Tue Nov 21 17:41:31 2006] [error] ajp_service::jk_ajp_common.c (1758):
Error connecting to tomcat. Tomcat is probably not started or is liste
ning on the wrong port. worker=ajp14 failed
then some hours and again the same msg
for the jk conf
worker.ajp14.port=9550
worker.ajp14.host=localhost
worker.ajp14.type=ajp13
worker.ajp14.lbfactor=50
worker.ajp14.cache_timeout=100
worker.ajp14.socket_keepalive=1
worker.ajp14.socket_timeout=30
Apache/2.0.59 tomcat 5.5.9 and 5.5.17 (they both do that)
most of the config is the default configuration, this do the same thing
on tomcat 5.5.
for apache config :
<IfModule mod_jk.c>
JkWorkersFile /usr/local/tomcat5/conf/workers2.properties
JkLogFile /var/log/jk.log
JkLogLevel emerg
JkLogLevel error
</IfModule>
and i call in the vhost tomcat like that Jkmount /* ajp14
OS : FreeBSD
it s mod_jk 1.2.15
thx
----- Original Message ----- From: "Rainer Jung"
<[EMAIL PROTECTED]>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Tuesday, November 21, 2006 4:23 PM
Subject: Re: tomcat stop working for some minute regulary
Please post your mod_jk config (Webserver part, eg. Jk* directoves in
httpd.conf, workers.properties, other relevant config and the
connector
element of the AJP connector in your timcat's server.xml). Also
give us
the version numbers of apache, tomcat, mod_jk and your OS. Finally: is
there anything elso in your mod_jk log or your tomcat logs around the
time of the problem?
[EMAIL PROTECTED] schrieb:
Hi, since few weeks i have a strange problem, sometimes tomcat stop
working and then come back (the site is unreachable and come back
few mn
after)
In the log i have :
[Tue Nov 21 15:03:11 2006] [error] ajp_service::jk_ajp_common.c
(1758):
Error connecting to tomcat. Tomcat is probably not started or is
listening
on the wrong port. worker=ajp14 failed
what could be the cause of that? (because tomcat is still listening)
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]
