throw new IllegalArgumentException("DeltaManager only
supports useDirtyFlag = true (yet). Maybe use
SimpleTcpReplicationManager instead.");
}
this.useDirtyFlag = useDirtyFlag;
}
----
Alex.
--
Alexander Schwar
e this connection
immediately without sending any other data. This should handle any
problems arising from chunked responses and/or content-length headers. But
I don't know how to implement that.
The included patch is only for jk, not jk2.
Alex.
--
Alexander Schwartz ([EMAIL PROTECTED])
htt
t fails after data has been sent to the
client, assume that the request is complete, i.e. return JK_TRUE
(otherwise apache will add some error messages to the reply).
Alex.
--
Alexander Schwartz ([EMAIL PROTECTED])
http://www.ahus1.de
till want to recover in this scenario?
Alex.
--
Alexander Schwartz ([EMAIL PROTECTED])
http://www.ahus1.de
package com.direkt1822.joba.filter;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.Filter;
import javax.serv
for 1.2.4/1.2.5, and I am happy to port it to
HEAD -- if someone checks that it leaves no loose ends.
Thanks for taking this serious.
Alex.
PS: this "empty POST" bug is not the explanation for the session mixup
(yet)? Any ideas on that one?
--
Alexander Schwartz ([EMAIL PROTECTED])
ht
x.servlet.http.HttpServletResponse;
/**
* This is a filter that sends all data sent from the client back to the client
* @author Alexander Schwartz (1822direkt) 2004
* @version $Id: EchoFilter.java,v 1.1 2004/01/22 12:10:39 ahus1 Exp $
*/
public class EchoFilter implements Filter {
pu
tes.
What I was able to test was empty POST after the first tomcat failed
while processing the request and mod_jk retried on another tomcat. Wait
for my jk.logs.
Alex.
--
Alexander Schwartz ([EMAIL PROTECTED])
http://www.ahus1.de
---
jk_log(l, JK_LOG_ERROR, "Error sending request body\n");
> > +// as+gj/20040123
> > +op->recoverable = JK_FALSE;
> > return JK_FALSE;
> > }
> > }
> > @@ -1279,6 +1295,9 @@
> >
t, but I need to make sure it's strong enough for production.
I need some advice on the two issues (as far as I can see there has been
no commit on CVS and/or discussion results)
* do you think the POST-recovery caused the session mix-up?
* does our patch successfully eliminate the proble
isms, but early and clean failure :)
Cheers, Alex.
--
Alexander Schwartz ([EMAIL PROTECTED])
http://www.ahus1.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
10 matches
Mail list logo