https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #27 from JasonDo ---
Dear all,
In our production environment, we did see mod_jk log print log.
Fri Mar 05 10:00:14.906 2021] [17221:139662211758208] [info]
ajp_handle_cping_cpong::jk_ajp_common.c (979): (worker3) timeout in
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
Mark Thomas changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #25 from Aurelien Pernoud ---
FYI I disabled the mod_jk debug to avoid having to clean it on a daily basis, I
will continue to monitor with mode "A" if the issue eventually comes back but
to me I would consider this one fix now ;)
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #24 from Aurelien Pernoud ---
2 weeks now, no error anymore.
I reactivated also mode "A" for 4 days now, still no error.
I will wait more as I'm not in hurry but honestly I think we can consider you
fixed it !
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #23 from Aurelien Pernoud ---
There is absolutely no hurry !
I've been working for a week almost now and no errors...
I'll leave it like that in our environment for the full month, I will even try
to reactivate the full mode "A" in
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #22 from Mark Thomas ---
The only thing that has changed as far as I know is Tomcat no longer always
does a blocking read after the CPing/CPong.
I still don't see how that could have caused the error though...
Could we give it
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #21 from Aurelien Pernoud ---
Hi Mark,
the error is not showing for 4 days. Is it possible that you or someone
actually fixed something in this patch too from version 9.0.26 ?? Or Should I
just wait a bit more...
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
Aurelien Pernoud changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #20 from
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #19 from Mark Thomas ---
Thanks for those logs. The Tomcat debug logs were useful. I'm now reasonably
sure Tomcat is closing the connection because of an IOException. However, the
logs don't show the exception. I have extended the
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #18 from Aurelien Pernoud ---
Of course I didn't mention that but the catalina logs is the one from
tom_tst01_srv09 !
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
Aurelien Pernoud changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #17 from Aurelien
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #16 from Aurelien Pernoud ---
Small update : I've been running for a week with CP, no error in the logs.
Will wait until next week and switch to CI see if it triggers the error or not.
--
You are receiving this mail because:
You
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #15 from Aurelien Pernoud ---
Hi Mark,
thanks for all the testing.
"It is interesting that - in the logs we have - it is only srv09 that is seeing
these errors. Is there something about those two instances that is unique?"
=>
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #14 from Mark
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #13 from Aurelien Pernoud ---
Thanks Mark,
appreciate all the time spent, I also agree this looks a complex one.
Reading mod_jk logs it seems the cping / cpong is not coming back but as you
also see the second httpd pointing to
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #12 from Mark Thomas ---
Thanks. I can't see anything obviously wrong in those files. The CPING is sent
and the CPONG is never seen.
If any Tomcat committer wants access to the logs, let me know and I'll send you
a link.
Debug
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #11 from Aurelien Pernoud ---
Thanks Mark, just uploaded everything.
in "logs" : mod_jk debug log from both httpd instances limited to the period
where the error occured
tom_tst01_srv09 is the full tomcat log
in "conf" :
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #10 from Mark Thomas ---
I'll send you a Google Drive link privately where you can upload the files.
Please upload the mod_jk debug logs, the Tomcat logs, the access log, the
mod_jk configuration files and the server.xml from the
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #9 from Aurelien Pernoud ---
I also collected tomcat logs even though I can't find anything in it, except
that "luckily" I also see for ex that our monitoring tool "pinged" (using HTTP
protocol) the server at [04/Nov/2019:09:15:02
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
Aurelien Pernoud changed:
What|Removed |Added
Status|NEEDINFO|NEW
--
You are receiving this
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #8 from Aurelien Pernoud ---
Hi Mark,
I have the debug but can't attach it due to limit of 1MB :-(
I managed to reproduce the issue, I have 2 httpd with the exact same
configuration, pointing to same tomcat.
In the logs of "http
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #7 from Mark
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #6 from Aurelien Pernoud ---
Tomcat 8.0.x
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail:
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #5 from Christopher Schultz ---
(In reply to Aurelien Pernoud from comment #3)
> Tomcat 7&8
Is this Tomcat 8.0.x or Tomcat 8.5.x?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #4 from Aurelien Pernoud ---
Also I even checked while the error was showing the "total connections" from my
httpd to tomcat 9 ajp port (netstat) : it was less than 10.
And when I stress test the ajp port, it worked. I'm lost :D
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #3 from Aurelien Pernoud ---
Hi Rainer,
Any info on usage characteristics during times this happens? High load (how
many requests per second), with or without load balancing, workers.properties
config etc.?
=> There is no "rule",
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #2 from Rainer Jung ---
Any info on usage characteristics during times this happens? High load (how
many requests per second), with or without load balancing, workers.properties
config etc.?
How frequently does it happen (always,
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
Aurelien Pernoud changed:
What|Removed |Added
CC||aurel...@pernoud.org
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
Aurelien Pernoud changed:
What|Removed |Added
OS||All
--- Comment #1 from Aurelien
29 matches
Mail list logo
