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
debug mode).
Removing this option, the test goes fine, nothing is logged (no INFO, no
WARN). With "-classic", it fails.
Do you know why ?
But I still don't understand why I have some exceptions running my webapps
in "real" separated tomcat... I've checked them, they don't have the
"-classic" option enabled, and I use the httpclient lib the same way I use
it in the testcase.
I'll check my code again and try to find what's happening there.
Aurelien Pernoud a �crit :
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 PROTECTED] a �crit :
19:24 ------- I have tried this new test case, but it seems to work fine for me. I'm running the servet in Tomcat 4.1.18 and have tried it with 1000 concurrent requests. Does this test fail for you?
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
