Sven Köhler schrieb:
>> Use mod_jk 1.2.15 and add:
>> JkOptions +FlushPackets
>
> That did the trick.
>
> But shouldn't this be enabled by default?
Why i say that:
- mod_jk shouldn't cause too many differences to using plain tomcat
- how big is this mod_jk/apache-internal buffer that is not flu
> Use mod_jk 1.2.15 and add:
> JkOptions +FlushPackets
That did the trick.
But shouldn't this be enabled by default?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Sven Köhler wrote:
If i load the page with FireFox directly by connecting to my Tomcat on
port 8080, it works fine. But if i load the page via apache/mod_jk on
port 80 it doesn't work.
mod_jk connects to the tomcat that also listenes on port 8080.
So something's pretty wrong here, don't you t
> If i load the page with FireFox directly by connecting to my Tomcat on
> port 8080, it works fine. But if i load the page via apache/mod_jk on
> port 80 it doesn't work.
By saying "it doesn't work" i mean, that the whole content is delayed by
3 seconds - so the flush() actually has no effect. Th
