Hallo Mladen,
>FlushPacket works, and the patch is invalid.
>The service ws_flush is invoked from ajp_common.
My original problem is that I produce a big servlet-response. This
servlet-response builds a progress-bar, so there are interruption (serversided
sleeps to wait for the next 'progress-bar-event') between some pieces of
html-parts. I want to send these chunks directly to the browser to update the
progress-bar but this did not heapen (without mod_jk it works). I tried to turn
off every buffer I found but it still did not work. Turning debug-level of the
mod_jk-log on I saw, that these parts where transmitted to the apache and the
apache does not transmit it to the browser. The patch was the only way to get
it work. Perhaps you could tell me how to solve this correctly - without a
patch?
>In theory there can be problems if there is no
>content_body packets, but the flushing is implied
>after the handler by apache itself.
As I explained I need flushed within the response after each chunk transmitted
from tomcat to apache not only at the end.
Regards,
Stephan
PS: My current configuration:
server.xml:
<!-- A AJP 1.3 Connector on port 8009 -->
<Connector port="8009" address="${jboss.bind.address}"
emptySessionPath="true" enableLookups="false" redirectPort="8443"
protocol="AJP/1.3" socketBuffer="-1" bufferSize="-1" />
httpd.conf:
JkWorkersFile "/appl/www/apache/etc/workers.config"
JkOptions FlushPackets
JkLogFile "/appl/www/apache/logs/mod_jk.log"
JkLogLevel warn
JkMount /* jboss
workers.config:
worker.list=jboss
worker.jboss.type=ajp13
worker.jboss.host=dpa.aomwebappl01.apa.at
worker.jboss.port=8009
worker.jboss.cachesize=0
-----Ursprüngliche Nachricht-----
Von: Mladen Turk [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 17. Februar 2006 11:43
An: Tomcat Developers List
Betreff: Re: Tomcat Connector 1.2.15 - JkOption "FlushPackets"-Bug
Pelikan Stephan wrote:
> Hello,
>
> I detected that the "FlushPackets" JkOption does not work. I could
> solve the problem by the patch
>
FlushPacket works, and the patch is invalid.
The service ws_flush is invoked from ajp_common.
In theory there can be problems if there is no content_body packets, but the
flushing is implied after the handler by apache itself.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
