Thanks.
Lot of amq switches
The trick is to set broker url =
failover:(tcp://localhost:61616)?jms.rmIdFromConnectionId=true&jms.prefetchPolicy.all=1&randomize=false&jms.redeliveryPolicy.maximumRedeliveries=0
to disable client side redelivery, and let the broker take control.
2014-09-03 12:57:0
On 09/01/2014 03:14 AM, preben wrote:
Good point.
I deleted the whole kahadb+tmp directory and started with a clean running
server, but the results are the same.
I'm still getting the default 6 amq redeliveries and then the broker
redelivery pluging kicks in on 7-10.
2014-09-01 09:01:10,224 |
Good point.
I deleted the whole kahadb+tmp directory and started with a clean running
server, but the results are the same.
I'm still getting the default 6 amq redeliveries and then the broker
redelivery pluging kicks in on 7-10.
2014-09-01 09:01:10,224 | INFO | Refreshing Root WebApplicationCo
On the test run that produced the log messages starting with redelivery #7,
was the entire test setup restarted fresh?
If not, try removing the entire kahadb, restart the clients, and try again.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/redeliveryPlugin-seems-to-ha
After turning tracing on it seems even more odd.
The redelivery plugin kicks in on redelivery 7. Seems that amq default
redelivery takes presens here
2014-08-29 14:23:52,927 | INFO | ActiveMQ WebConsole available at
http://0.0.0.0:8161/ | org.apache.activemq.web.WebConsoleStarter | main
2014-08-
Doesn't seem to make any difference.
DefaultEntry is not taken into account, only the direct
redeliveryPolicyEntries seems to work if you set a queue property that
matches a queue.
eg.
Use wildcard ">" to replace "*" for property "queue"
--
View this message in context:
http://activemq.2283324.n4.nabble.com/redeliveryPlugin-seems-to-have-problems-with-defaultEntry-tp4685094p4685102.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
