> - Are the results I get from those 3 examples
> "expected" ?
I actually tried to reproduce your experience.
wget, FireFox etc. - all these HTTP-clients don't have any problems with
tomcat.
What HTTP-client are you using? Is it self-written maybe?
signature.asc
Description: OpenPGP digi
>> Any ideas?
>
> Any ideas why tomcat 6.0.10 doesn't send flush packets? I should see
> them in mod_jk's log, right? (JkLogLevel is debug)
The explanation is:
Is the JNI APR stuff is installed, Tomcat will use
org.apache.coyote.ajp.AjpAprProtocol.
Not the JNI APR stuff is NOT installed, Tomcat
> in mod_jk's logfile, i don't see any flush-packets (= write packet of
> length 0) and so apache doesn't do flushing either.
>
> Of course the old "JkOption +FlushPackets" works.
> But the new flush-packets would be much nicer.
>
> I think, that i might have to enable the flush-packets thing wit
> Any ideas?
Any ideas why tomcat 6.0.10 doesn't send flush packets? I should see
them in mod_jk's log, right? (JkLogLevel is debug)
signature.asc
Description: OpenPGP digital signature
Hi,
in mod_jk's logfile, i don't see any flush-packets (= write packet of
length 0) and so apache doesn't do flushing either.
Of course the old "JkOption +FlushPackets" works.
But the new flush-packets would be much nicer.
I think, that i might have to enable the flush-packets thing within tomca
> Oh! This sounds, like it's a "bug" and like it might be fixed in tomcat
> 6, for example. Now i'm curious, and will test tomcat 6 ...
Ahh damn - i didn't read properly.
It's the old story: it's NOT a bug, it's a feature ;-)
signature.asc
Description: OpenPGP digital signature
>> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Sven Köhler
>> Subject: charset for querystring decoding
>>
>> And if you know: what's the reason, that the charset is not
>> configurable via request.setCharacterEncoding() ?
>
> Might want to che
Hi,
as far as i remember, tomcat always uses a default-charset for decoding
the querystring. A call to request.setCharacterEncoding() only matters
for decoding POST-data.
Somewhere, this charset can be changed - for example to UTF-8.
Where can it be changed?
And if you know: what's the reason, t
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/
> 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]
> 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
Hi,
take a look at the following JSP-page:
<[EMAIL PROTECTED] contentType="text/plain"%>
<%
out.println("this should appear immediatly");
out.flush();
Thread.sleep(3000);
out.println("this should appear after 3 seconds");
%>
If i load the page wi
> The system seems to work fine from a user's
> perspective, but we still occasionally get these:
>
> [Wed Mar 01 20:00:42 2006] [error]
> ajp_connection_tcp_get_message::jk_ajp_common.c (961):
> Can't receive the response message from tomcat,
> network problems or tomcat is down (10.0.0.9:8009),
> But there is something i should first look at before i further complain:
> some ServletFilters. Maybe one called getParameter() which could be the
> cause.
Yes, one of the servletfilters calls getParameter() on the request.
Sorry for taking your time.
-
>> The above JSP-page will not work properly. The POST-data is decoded with
>> ISO-8859-1 instead of UTF-8 in Tomcat 5.5.
> Works for me using the latest 5.5 from svn.
interesting! (and at least, there's some hope for me :-) )
> It would be a bug but since it is working for me it looks like a
> c
Hi,
<[EMAIL PROTECTED] contentType="text/html; charset=UTF8"%>
<%
request.setCharacterEncoding("UTF-8");
%>
Test: <%=request.getParameter("text")%>
The above JSP-page will not work properly. The POST-data is decoded with
ISO-8859-1 instead of UTF-8 in Tomcat 5.5.
Is this a bug or
16 matches
Mail list logo
