On Sun, 2006-02-19 at 23:33 -0800, Marc de Klerk wrote:
I must be subscribed there by mistake... It would be great if I was
unsubscribed.
Fair enough. Instructions for doing so appear, as with most mailing list
email nowadays, at the bottom of each article. From your own reply:
To
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
I thing you mus set
JkOptions +FlushPackets
regards
Peter
Am 20.02.2006 um 09:28 schrieb Pelikan Stephan:
JkOptions FlushPackets
hi,
I downloaded the tomcat 5.5.15 source code. and made the build sucessfully.
then i saw an ant task in build/build.xml called test and try to run (saying
ant test) the task.
but there were some compilation errors.
are they obselete or else can someone explain me how to build and run the
tests.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38716.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Are you sure that + is the default for the FlushPackets option? I had a
similar issue where I was trying to stream data from a servlet. Once I
added 'JkOptions +FlushPackets' to my mod_jk config, everything worked
as expected.
,
Josh.
-Original Message-
From: Mladen Turk
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38716.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Hi Mladen,
are you sure? I have the impression default is
c-options = JK_OPT_FWDURIDEFAULT;
and
#define JK_OPT_FWDURIDEFAULTJK_OPT_FWDURICOMPAT
#define JK_OPT_FWDURICOMPAT 0x0001
but needed is
#define JK_OPT_FLUSHPACKETS 0x0020
It looks like JK_OPT_FLUSHPACKETS is
Rainer Jung wrote:
Hi Mladen,
are you sure? I have the impression default is
I meant that the '+' is default:
if (action == '-') {
conf-options = ~opt;
}
else if (action == '+') {
conf-options |= opt;
}
else { /* for now +Opt == Opt */
conf-options |= opt;
}
So
Author: remm
Date: Mon Feb 20 09:45:48 2006
New Revision: 379183
URL: http://svn.apache.org/viewcvs?rev=379183view=rev
Log:
- Slightly modify the timing of the manager start (unfortunately, setManager in
ContextConfig.java
causes and immediate start of the manager).
Modified:
Author: markt
Date: Mon Feb 20 10:02:51 2006
New Revision: 379187
URL: http://svn.apache.org/viewcvs?rev=379187view=rev
Log:
enum - enumeration to allow building on Java 5.0 generally and Gump in
particular without having to set source compatibility to 1.4 or lower.
Modified:
Author: markt
Date: Mon Feb 20 10:03:47 2006
New Revision: 379188
URL: http://svn.apache.org/viewcvs?rev=379188view=rev
Log:
enum - enumeration to allow building on Java 5.0 generally and Gump in
particular without having to set source compatibility to 1.4 or lower.
Modified:
Hi List,
please somebody explain:
every few days, a strange procedure can be seen on this list.
Somebody asks for improvement, suggests a fix or simply wants to discuss a new
feature.
Few minutes later, there is an answer from somebody, which tells us to ignore
this subject, because it is not
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project tomcat-jasper_tc6 has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project tomcat-jasper_tc6 has an issue affecting its community integration.
This issue
+1
=)
Reinhard Moosauer wrote:
Hi List,
please somebody explain:
every few days, a strange procedure can be seen on this list.
Somebody asks for improvement, suggests a fix or simply wants to discuss a new
feature.
Few minutes later, there is an answer from somebody, which tells us to
RESOLVED | INVALID
George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
-Original Message-
From: Reinhard Moosauer [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 11:09 AM
To: tomcat-dev@jakarta.apache.org
Subject: never say never...
Hi
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38716.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
I really try to avoid these threads cause I'm not interested in debates
nor the political aspects of open source projects and how they work,
but the user brings up a good point, with a probable solution, and I
don't see how a non committer response like the one below is even justified.
I'm not
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 1:52 PM
To: Tomcat Developers List
Subject: Re: never say never...
nor the political aspects of open source projects and how they work,
This is a topic in which you should
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38726.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
George Sexton wrote:
Whilst I agree with the general thrust of the arguments made so far in
this thread I do take serious issue with one of your statements.
Just as a little example, several months ago I submitted a patch. One
committer commented that he would -1 it for the com.sun imports.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38716.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
-Original Message-
From: Mark Thomas [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 4:02 PM
To: Tomcat Developers List
Subject: Re: never say never...
George Sexton wrote:
Whilst I agree with the general thrust of the arguments made so far in
this thread I do take
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38726.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
-Original Message-
From: Mark Thomas [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 4:02 PM
To: Tomcat Developers List
Subject: Re: never say never...
I agree that closing bug reports without an explanation is rarely, if
ever helpful. A few lines explaining why the
George Sexton wrote:
Don't misunderstand me. I'm certainly not saying a committer shouldn't say
This is non-compliant and will not be addresed or We comply with the
spec, and we will not be expanding the application to meet your specific
need. These are legitimate responses.
Agreed.
When the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38726.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
-Original Message-
From: Mark Thomas [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 5:33 PM
To: Tomcat Developers List
Subject: Re: never say never...
On the subject of fairness, is it fair that someone who is too lazy to
read the spec / read the docs / etc should
A disclaimer here - I used to have committer status (and might still).
On 2/20/06, George Sexton [EMAIL PROTECTED] wrote:
As far as how to structurally fix the tomcat group, my only feeble
suggestion would be to permit TOMCAT USERS to recall or fire committers.
Perhaps then some of the more
-Original Message-
From: Preston L. Bannister [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 6:22 PM
To: Tomcat Developers List
Subject: Re: never say never...
A disclaimer here - I used to have committer status (and might still).
On 2/20/06, George Sexton [EMAIL
Mark Thomas [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Stefan Bodewig wrote:
Project tomcat-catalina has an issue affecting its community integration.
This issue affects 9 projects.
The current state of this project is 'Failed', with reason 'Build
Failed'.
Should be fixed
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project jakarta-tomcat-4.0 has an issue affecting its community integration.
This issue
hi,
following is the error I got
Buildfile: build.xml
test:
[echo] Target: Catalina - Test ...
test:
[echo] Target: Catalina - Test ...
flags:
flags.display:
[echo] --- Build environment for Catalina ---
[echo] If ${property_name} is displayed, then the property is not
34 matches
Mail list logo
