Avoid adding known messages to DLQ when exception thrown and keep in queue

[kavinthamaduranga]

hi, following is my mdb annotations and i'm using jboss EAP 7

@MessageDriven(name = "ConnectPublish_upp", activationConfig = {

    @javax.ejb.ActivationConfigProperty(propertyName = "destinationLookup", propertyValue = "topic/L_upp"),

    @javax.ejb.ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic"),

    @javax.ejb.ActivationConfigProperty(propertyName = "destination", propertyValue="topic/L_upp"),

    @javax.ejb.ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue="Durable"),

    @javax.ejb.ActivationConfigProperty(propertyName = "subscriptionName", propertyValue="lUpp"),

    @javax.ejb.ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge") })

So when a RunTimeException occur in "onMessage" , message will be added to DLQ as default behavior. how to avoid that keep the queue grow?

[jbertram]

how to avoid that keep the queue grow?

Are you asking how to avoid growth of the DLQ?  If so, possible solutions might be:

• Change the broker configuration so that messages aren't sent to the DLQ
• Set up an MDB on the DLQ itself and deal with the messages when they arrive
• Periodically survey the messages and delete them administratively

[kavinthamaduranga]

Thanks jbertram for the reply and figured out can be set the address setting to set the re-delivery limit before add to the DLQ