if anything has changed since then (May '08). For
> > ActiveMessaging, it looks like Andrew implemented his own max retry logic
> > (
> >
> https://trac-git.assembla.com/breakout/browser/vendor/plugins/activemessaging/lib/activemessaging/adapters/stomp.rb?rev
sembla.com/breakout/browser/vendor/plugins/activemessaging/lib/activemessaging/adapters/stomp.rb?rev=a288646f5565a84e1358d827e889b13ea73abca4
> )
>
> Thanks,
>
> Roger
>
>
--
View this message in context:
http://www.nabble.com/STOMP-redelivery-policy-tp22141094p23390201.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Is there any way to configure maximumRedeliveries for a STOMP connection?
I ran tests against 5.2 and 4.1.1 and both redeliver the message
infinitely. This causes consumers to keep choking over and over again on
the same message unless the consumers implement their own maxRetries logic.
It looks
