Hmm I have a beginning of explanation, though I don't understand why this
may cause the test to fail.
I was running Tomcat via JBuilder, and using the -classic option (for
debug mode).
Removing this option, the test goes fine, nothing is logged (no INFO, no
WARN). With -classic, it fails.
Do you
Is this classic option the JVM -classic flag?
Mike
On Monday, February 24, 2003, at 04:45 AM, Aurelien Pernoud wrote:
Hmm I have a beginning of explanation, though I don't understand why
this
may cause the test to fail.
I was running Tomcat via JBuilder, and using the -classic option (for
Well yes when I tried it Friday it failed a lot, I got some responses
exchanged
(error : I asked for 458 and I got 269 for example)...
I'll retest it today, but It sure did fail, or maybe I drank too much, but
usually I don't at work... :))
I too tested it in tomcat 4.1.18, weird.
[EMAIL
Well, as some changes have been made to httpmethodbase between yesterday
evening, and lines changed were about connection, I tried with current CVS,
still the same :(
I have a little time this afternoon, so I'll try to write a test case, but
this test case may need a servlet on the other part
Thx to everyone for help, and sorry Mike I made you spend some time on
it, I
hate it :
Not to worry. You've discovered some legitimate bugs in HttpClient's
multi-threaded support.
Mike
-
To unsubscribe, e-mail: [EMAIL
Michael Becke a ecrit :
Thx to everyone for help, and sorry Mike I made you spend some time
on it, I hate it :
Not to worry. You've discovered some legitimate bugs in HttpClient's
multi-threaded support.
Mike
I just downloaded and compiled httpclient from current cvs, I'll try your
