JMS and MessageDriven Bean

[Fernando Franzini]

Hello Rancher

In setting a MessageDriveBean asynchronous insert a record in a relational database. What to do in case of communication problems?
My doubt is ... the setting that makes the MDB run several times until the relational database back is done in a proprietary extension on each application server?
Has anyone had experience in context?

Regards.

[Lucas Smith]

Hi Fernando,

When there will be communication problems with DB the exception will be thrown from your MDB. JMS provider will attemp to redeliver such message. It can be potentially dangerous (poison message) unless you specify the number of redelivery attempts. After specified number of attempts your message will be send to the special place and you can monitor it.

[Fernando Franzini]

Hi Lucas

This configuration is done in a proprietary extension on each application server?
Regards

[Lucas Smith]

Exactly!
The example for JBoss:
http://middlewaremagic.com/jboss/?p=2402

Important piece of configuration
<address-settings> <address-setting match="jms.queue.MyQueue"> <dead-letter-address>jms.queue.MyDLQ</dead-letter-address> <redelivery-delay>0</redelivery-delay> ->>> Interval between redelivery attempts. <max-delivery-attempts>3</max-delivery-attempts> <max-size-bytes>10485760</max-size-bytes> <address-full-policy>BLOCK</address-full-policy> <message-counter-history-day-limit>10</message-counter-history-day-limit> </address-setting> </address-settings>

[Fernando Franzini]

That was exactly what I needed to know Lucas!
Best Regards.