{"id":477,"date":"2010-03-18T12:04:52","date_gmt":"2010-03-18T06:34:52","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=477"},"modified":"2010-06-09T15:34:58","modified_gmt":"2010-06-09T10:04:58","slug":"grails-jms-plugin-and-redelivery-policy","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/grails-jms-plugin-and-redelivery-policy\/","title":{"rendered":"Grails JMS Plugin and Redelivery Policy"},"content":{"rendered":"

On a project, we needed to configure the redelivery mechanism for the JMS queue. That is, a poisonous message was to be sent to a Dead Letter Queue if a set number of attempts failed, so that the other messages in the queue could be processed. The JMS Plugin version used was 0.5<\/p>\n

Merely configuring ActiveMQ for setting up a Dead Letter Queue like :<\/p>\n

<policyEntry queue=”>” memoryLimit=”5mb”>
\n<deadLetterStrategy>
\n<individualDeadLetterStrategy queuePrefix=”DLQ.” useQueueForQueueMessages=”true” \/>
\n<\/deadLetterStrategy>
\n<\/policyEntry><\/p><\/blockquote>\n

And injecting the bean redeliveryPolicy into jmsConnectionFactory bean inside resources.groovy like this:<\/p>\n

\n
jmsRedeliveryPolicy(org.apache.activemq.RedeliveryPolicy){\r\n        maximumRedeliveries = 3\r\n        initialRedeliveryDelay = 500L\r\n        backOffMultiplier = 2\r\n        useExponentialBackOff = true\r\n    }\r\n    jmsConnectionFactory(org.apache.activemq.ActiveMQConnectionFactory) {\r\n        brokerURL = 'tcp:\/\/localhost:61616'\r\n        redeliveryPolicy = jmsRedeliveryPolicy\r\n    }\r\n<\/pre>\n<\/blockquote>\n
did not do the trick. When an exception was thrown in the listener method in any service exposed to JMS, the message was staying in the queue and halting processing of subsequent messages.<\/p>\n
A change in the configuration of the “standard” container was required and this was done in Config.groovy as :<\/p>\n
\n
jms {\r\n    containers {\r\n        standard {\r\n            sessionTransacted = true\r\n        }\r\n    }\r\n}\r\n<\/pre>\n<\/blockquote>\n
This did the trick and the redelivery policy and dead letter queue mechanism started working the way we wanted it to.<\/p>\n
Hope it helps<\/p>\n
Vivek<\/p>\n","protected":false},"excerpt":{"rendered":"
On a project, we needed to configure the redelivery mechanism for the JMS queue. That is, a poisonous message was to be sent to a Dead Letter Queue if a set number of attempts failed, so that the other messages in the queue could be processed. The JMS Plugin version used was 0.5 Merely configuring […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":15,"footnotes":""},"categories":[7],"tags":[187,4840,186,190,188],"class_list":["post-477","post","type-post","status-publish","format-standard","hentry","category-grails","tag-activemq","tag-grails","tag-jms","tag-jms-plugin-0-5","tag-redelivery-policy"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t