de/configuration.
Thanks again for your help Tim.
I will try to see what’s under the hood in the Spring DMLC when heavy
message has failed due to transaction timeout and if upgrading to 5.10.0
solves our issues. I will write when I am done with these two.
Regards
Marek Dominiak
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Not-abortable-slow-consumers-stopped-processing-of-messages-in-a-queue-tp4686721p4686838.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi Tim,
Thank you for your input and sharing your experience and knowledge.
tbain98 wrote
> 1. In my limited experience with slow consumer abort strategies (using
> the
> SlowConsumerAbortStrategy, not the SlowAckConsumerAbortStrategy), I've
> observed that a client will continue processing the
ers (
failover:(tcp://localhost:61616)?jms.redeliveryPolicy.maximumRedeliveries=0
) and the aborted connection had maximumRedeliveries set to 1 the new
connection got the default redelivery policy (6 redeliveries).
Any help is appreciated.
Thanks in the advance.
Regards
Marek Dominiak
--
V
a/beans";
class="org.apache.activemq.hooks.SpringContextHook"/>
Any ideas / help is appreciated.
Thank you in the advance.
Regards
Marek Dominiak
--
View this message in context:
http://activemq.228332
