Yes, I do mean duplicate requests. I know they are duplicates because the header contains the unique (thread-safe) counter that my test harness increments. Each request should contain its unique "request count", but some requests contain counts already seen before -- hence they are being duplicated/resent for some reason by something which is not my web app nor my test harness.
I maintain a unique thread-safe count in the test harness. That shows the test is sending the correct number of requests. On the server-side in the Jersey resource end-point, purely for debug purposes, I am using a bitset to maintain the counts already seen from the headers of the incoming requests. That demonstrates that I am receiving duplicate requests on the server. Everything is standalone on my machine. Nothing else is using the web app as it's a greenfield project under my sole development. It's the standard standalone Tomcat configuration. My web app uses 2-legged OAuth for authentication using a Jersey ResourceFilter. That has always worked and is not the cause of any failures. In fact, all of my Jersey client requests from the test harness return 200 response codes. I'll run Tomcat 7 and check the access logs. -- View this message in context: http://old.nabble.com/Tomcat-appears-to-be-sending-duplicate-requests-tp32019702p32020307.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
