[esb-issues] [JBoss JIRA] Created: (JBESB-3597) DLQ handling on JCA side causes duplicate redelivery to DLQ

[Toshiya Kobayashi (JIRA)]

DLQ handling on JCA side causes duplicate redelivery to DLQ
-----------------------------------------------------------

                 Key: JBESB-3597
                 URL: https://issues.jboss.org/browse/JBESB-3597
             Project: JBoss ESB
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Adapters, Examples
    Affects Versions: 4.9 CP1
            Reporter: Toshiya Kobayashi


JCA DLQ handling interferes with JBM DLQ handling and may end up with unexpected results. You can find discussions in JBAS-7465 and JBPAPP-3352.

In ESB, you can reproduce the issue with jms_transacted quickstart.

====================
- Edit jboss-esb.xml to set dLQMaxResent=3

<property name="dLQMaxResent" value="3"/>

- ant deplpy

- ant runtest

The message will be sent to DLQ.

- Check jboss.messaging.destination:name=DLQ,service=Queue via jmx-console

You will see MessageCount=1

- Check jboss.esb.quickstart.destination:name=quickstart_jms_transacted_Request_esb,service=Queue via jmx-console

You will see MessageCount=1, DeliveringCount=1 though the message has been sent to DLQ.

- ant deploy

Redeploying the queue causes re-delivering the message to DLQ

- Check jboss.messaging.destination:name=DLQ,service=Queue via jmx-console

You will see MessageCount=2 (duplicate).
=====================

Looking at JBAS-7465 and JBPAPP-3352, there is less chance to resolve the root issue from AS/JBM side. I filed this JIRA for something we can address from ESB side.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira