Thanks for the info Gary. Summarizing the info in that JIRA, I believe the answer is "If you've set 'jms.nonBlockingRedelivery=true' on your URL, message processing will continue during the redelivery interval, and the redelivered message will be re-processed out-of-order once the redelivery interval elapses. If not, then the consumer will block until the message is successfully processed or the max number of retries is reached. Both of these apply no matter whether the message is in a message group or not." Does that cover it?
Tim On Fri, Apr 24, 2015 at 7:43 AM, Gary Tully <[email protected]> wrote: > there is some good info in https://issues.apache.org/jira/browse/AMQ-1853 > > short answer: the ordered blocking consumer side is configurable but > it is independent of jms message groups > > On 6 April 2015 at 11:09, cduvvuri <[email protected]> wrote: > > Would ActiveMq holds ordered messages delivery until the first message > > delivery(if failes) is retried as per configuration. > > > > For example, if a processing exception is thrown and a retry policy is > setup > > to retry 3 times every 10 seconds....will the next message in this > "group" > > be processed during that time period or only after the retries have > > completed? > > > > > > > > -- > > View this message in context: > http://activemq.2283324.n4.nabble.com/Message-Grouping-Retry-Policy-tp4694353.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
