Awesome, that's exactly what I was looking for. Thanks!
Geoff.
On Oct 21, 2009, at 3:01 PM, Drizzt321 wrote:
I think that would be specifying jms.prefetchPolicy.queuePrefetch=0
as part
of your connection string. This turns off the Consumer prefetch
queue that
you seem to be talking about. It can impact performance though. See
http://activemq.apache.org/what-is-the-prefetch-limit-for.html
Geoffrey Arnold-2 wrote:
Thanks Gary. Our Cucumber tests are really integration tests, so it
would require a restart of the VM running the embedded broker.
Is there anyway to disable the internal queue?
On Oct 16, 2009, at 6:28 AM, Gary Tully wrote:
I guess it is typical to use a new session per test unless it is the
session
behavior that is under test?
2009/10/15 Geoffrey Arnold <geoff...@geoffreyarnold.com>
Hi All,
We are successfully using JMX to purge our queues in between our
Cucumber-based test scenarios, however this does not clear the
session's
internal consumer queue. This can cause messages which have been
delivered
to the consumer's session but not yet consumed by the listener
(perhaps
because of an initial delivery failure) to be redelivered in
subsequent test
scenarios.
What strategies are you using to purge (or completely disable) the
internal
consumer queue?
Thanks,
Geoff.
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
--
View this message in context:
http://www.nabble.com/Strategies-for-purging-internal-consumer-queue-tp25915202p25998296.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
