-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pid/Hans,
On 8/16/2010 5:53 AM, Pid wrote: > On 16/08/2010 09:52, Hans Wahn wrote: >> I'd like to provide more information. Any suggestions what is the best >> way to accomplish that? > > See above, regarding trace log. > > Also, providing a stack trace if there is one from the error log and any > access log data. > > You might consider *not* sending the 100 header and just proceeding as > normal. Also, can you try your tests against a similarly-configured Tomcat 6.0.29 instance? It may be that some code has changed in Tomcat 7 and some regression occurred. Especially if you have a super-simple test case (and it looks like you do: you have an automated client that makes a limited and deterministic set of requests, and you can probably whip-together a skeleton webapp that behaves badly on command), you should probably file this as a bug and submit everything you've got: HTTP conversation logs, the example webapp, and the automated client. You'd be amazed how fast a reproducable bug can be fixed ;) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxsrQUACgkQ9CaO5/Lv0PDeOACfR5A4AkbA5JxEX5zihfSAL9BS c4kAnRQB0BT8N8jUO65Oniq0y1e0QGB5 =6gqR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
