[jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1858) DLQ handling on JCA side causes duplicate redelivery to DLQ

[Toshiya Kobayashi (JIRA)]

     [ https://issues.jboss.org/browse/JBMESSAGING-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Toshiya Kobayashi reassigned JBMESSAGING-1858:
----------------------------------------------

    Assignee: Yong Hao Gao


> DLQ handling on JCA side causes duplicate redelivery to DLQ
> -----------------------------------------------------------
>
>                 Key: JBMESSAGING-1858
>                 URL: https://issues.jboss.org/browse/JBMESSAGING-1858
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: AS Integration, Messaging Core
>    Affects Versions: 1.4.7.GA
>            Reporter: Toshiya Kobayashi
>            Assignee: Yong Hao Gao
>         Attachments: reproducer.zip
>
>
> JCA DLQ handling with JBM may end up with unexpected results. 
> ====================
> - Download and unzip attached reproducer.zip
> - Edit build.properties
> - ant deployQueue
> - ant deploy
> - ant run
> A client sends a meesage. The MDB causes rollback and then the messege goes to DLQ by JCA DLQ handling
> - Check jboss.messaging.destination:name=DLQ,service=Queue via jmx-console
> You will see MessageCount=1 (OK)
> - Check jboss.messaging.destination:name=A,service=Queue via jmx-console
> You will see MessageCount=1 and DeliveringCount = 1 (Not OK)
> - Stop and start jboss.messaging.destination:name=A,service=Queue via jmx-console
> You will see MessageCount=2 and DeliveringCount = 2 (Not OK)
> - Check jboss.messaging.destination:name=DLQ,service=Queue via jmx-console
> You will see MessageCount=2 (Not OK)
> =====================
> You can find some discussions in JBAS-7465 and JBPAPP-3352.

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