Support Article

Campaign hangs after Campaign with Constraint

SA-30817

Summary



Post a Campaign being run that uses a Constraint, all subsequent Campaigns hang in the "Upcoming state".

Agents including the SLA agent stop running and the next processing date remains in the past.

Error Messages



Not applicable


Steps to Reproduce



Run Campaign 1, run Campaign 2, run campaign 3 with a Constraint, run campaign 4. Campaign 4 will remaining in "Upcoming" and will never run.


Root Cause



Issue was specific to JBOSS configuration.

Resolution


Perform the following local-change:

Update JBOSS configuration ‘standalone-full.xml’ to disable buffering at user end:

Set “consumer-window-size” to 0 to allow slow consumers, set the consumer-window-size to 0 (for no buffer at all).

​This will prevent the slow consumer from buffering any messages on the client side. Messages will remain on the server side ready to be consumed by other users.

<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<consumer-window-size>0</consumer-window-size>
</pooled-connection-factory>


2. Set “max-delivery-attempts” to 1

<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>10485760</max-size-bytes>
<page-size-bytes>2097152</page-size-bytes>
<address-full-policy>PAGE</address-full-policy>
<max-delivery-attempts>1</max-delivery-attempts>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
</address-setting>


Published November 25, 2016 - Updated August 23, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.