On 07/27/2014 10:04 PM, Kevin Burton wrote:
I'm having a difficult time getting redelivery to work.
All the tests seem to have redelivery specified in the client.
Which I don't understand because this seems dangerous. If a client were to
connect without redelivery settings, its messages would never get
re-executed.
The client has default settings for redelivery, see RedeliveryPolicy.
If the client goes down it's messages that are pending (unacknowledged)
get redelivered to another client, no loss.
So I've been using the redelivery plugin … but I can't get it to work.
This test:
https://github.com/apache/activemq/blob/a3a41dae3711f01e13110ed266e9e825b710e986/activemq-unit-tests/src/test/java/org/apache/activemq/broker/BrokerRedeliveryTest.java
uses the redelivery plugin. BUT, it also specifies client settings for
redelivery.
1. Are client settings required even for the plugin?
The test settings simply reduce the amount of time it'd take the test to
run by immediately rejecting the rolled back messages instead of
re-delivering them locally based on the default policy settings.
2. isn't it dangerous to require the client to specify redelivery
settings? If you created one without those settings the client may just
start dropping messages.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
[email protected] | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
