| Field |
Original Value |
New Value |
|
Description
|
Two bundles are used to test this (attached in MB-934):
- a producer (pinger) that makes a request via a Camel inOut("activemq:...") and waits for a response
- a consumer (ponger) that pulls from that queue and responds on a temporary queue
Two Smx instances are set up with the pinger bundle, one is set up with the ponger, and tied together through a single Amq instance. A load test is set up using JMeter to hit the ping web service with 100 threads repeatedly, and run against both Smx instances simultaneously. After a handful of requests, the producer bundles start throwing exceptions about exceeded timeouts on the inOut() segment.
No exceptions are seen from the ponger bundle.
|
Two bundles are used to test this (attached in ESB-1573):
- a producer (pinger) that makes a request via a Camel inOut("activemq:...") and waits for a response
- a consumer (ponger) that pulls from that queue and responds on a temporary queue
Two Smx instances are set up with the pinger bundle, one is set up with the ponger, and tied together through a single Amq instance. A load test is set up using JMeter to hit the ping web service with 100 threads repeatedly, and run against both Smx instances simultaneously. After a handful of requests, the producer bundles start throwing exceptions about exceeded timeouts on the inOut() segment.
No exceptions are seen from the ponger bundle.
|
Bug
Open
Major
Request-response messaging over temp queues locks up on load from multiple producer bundle instances
