Alright, thanks for your explanation!
Are the mod_jk: error flushing messages more or less harmless? If so, I
prefer sticking to 1.2.6 for the moment.
Durk
Hi Durk,
the flushing has been changed in May 2005 around the time of version
1.2.13 or 1.2.14. Previously there were a lot of calls to
Thanks for looking into the source code.
Well as long as no functional or performance problems arise in our web
applications it seems to be okay. But, of course, the error messages are not
really satifying.
Anyway, I'll keep in mind that versions of mod_jk from 1.2.14 and above will
not be able
Hi Durk,
are you really talking about mod_jk?
Yep, the package apache2-jakarta-tomcat-connectors contains (from the
included README file):
1. mod_jk + Ajp13Connector
2. mod_jk2 + CoyoteConnector + JkCoyoteHandler
3. mod_webapp + WarpConnector
2 is experimental, 3 is deprected, we're using
Hi Durk,
the flushing has been changed in May 2005 around the time of version
1.2.13 or 1.2.14. Previously there were a lot of calls to ap_rflush()
during the writing of responses. Because that produced many problems
(not only log messages) concerning performance and memory requirements,
these
Hi all!
I'm wondering the same.
I've got four servers (two production machines and their testing counter
parts) running SUSE Linux Enterprise Server 9 with Apache 2, Tomcat 5, and
ModJK. Below the relevant packages are shown:
apache2 2.0.49-27.59
apache2-prefork
Hello there,
Does anyone know what is this 'mod_jk: error flushing' about? I am using
Tomcat 5.0, Apache and Mod_JK in production environment and keep getting
this error in error log. I do google search and find lots of persons
asking this question but no answer. Can anybody having experience
