How to solve HornetQ message block (HQ214024) by setting it to paging mode. Jboss EAP 6.1

Using OOTB clustering, when performing bulk operations you may get HornetQ to block accepting new transactions showing the following messages in the server.log

HQ214024: Destination address=jms.queue.iam.im.jms.queue.com.netegrity.ims.msg.queue is blocked. If the system is configured to block make sure you consume messages on this configuration.

 

Below is a sample Paging mode setting that help you overcome the immediate problem.

To set paging apply the following to each node of the cluster:

1. Open JBOSS_HOME\Stanalone\configuration\standalone-full-ha.xml for editing.
2. Locate the two entries for address for setting “#” (<address-setting match="#">)
3. Set the entry to look as so (Note: changed are marked in bold captions):

<address-setting match="#">

<dead-letter-address>jms.queue.DLQ</dead-letter-address>

               <expiry-address>jms.queue.ExpiryQueue</expiry-address>

               <redelivery-delay>0</redelivery-delay>

               <max-size-bytes>104857600</max-size-bytes>

               <page-size-bytes>10485760</page-size-bytes>

               <address-full-policy>PAGE</address-full-policy>

               <message-counter-history-day-limit>10</message-counter-history-day-limit>

               <redistribution-delay>1000</redistribution-delay>

</address-setting>

1. Save the file and restart both nodes in an orderly fashion.

 

For more information about HornetQ Paging see the following links (many others available online):

 

Jboss AS:

http://docs.jboss.org/hornetq/2.2.5.Final/user-manual/en/html/paging.html#paging.mode

 

Jboss EAP 6:

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Administration_and_Configuration_Guide/chap-Messaging.html#sect-HornetQ

 

Official HornetQ guides:

http://hornetq.jboss.org/docs