>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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 7/8/2011 12:29 PM, peterjca wrote:
> Taking the web service request for the computation step out of my
> harness results in my app behaving correctly. Some of the computation
> web service requests are randomly being routed to the wrong
> en
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
peterjca wrote:
It's running now on Tomcat 7. I've had duplicate requests so checked the
access logs. All requests have 200 response code.
:confused:
Hi.
I am not going to provide the solution, just intervening on the "form" aspect
of the dialog.
You have obviously put a lot of effort in chec
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
On 08/07/2011 11:07, peterjca wrote:
>
> 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 alread
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
2011/7/8 Peter Cameron :
> I'm having an interesting problem which seems to be Tomcat-related and which
> occurs randomly under heavy load. I'd appreciate some advice/help.
>
> I'm developing a Java web application and deploying to Tomcat 6.0.32. (I get
> the same behaviour with the latest Tomcat 7
