>Now you just need a test harness for your test harness. :)
Ad infinitum!
It's not strictly a bug in the harness. The test harness implements one
correct scenario for a concurrent "thrashing". It uses the Jersey client API
to post requests, by constructing a new client each time. The only state
Thanks for your response. Yes, I was a bit sloppy with my "sending requests"
language. Also, I'm not saying that third party libraries used by my code
aren't to blame. Certainly something in between obviously is... ...and I've
just found out what.
There are two web service endpoints being used by
It's running now on Tomcat 7. I've had duplicate requests so checked the
access logs. All requests have 200 response code.
:confused:
--
View this message in context:
http://old.nabble.com/Tomcat-appears-to-be-sending-duplicate-requests-tp32019702p32020404.html
Sent from the Tomcat - User maili
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
duplicate
