[jboss-jira] [JBoss JIRA] (AS7-4203) Persistent messages sent to JMS destinations deployed via a war file do not recover after a crash

[Andy Taylor (JIRA)]

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

Andy Taylor reassigned AS7-4203:
--------------------------------

    Assignee: Jeff Mesnil  (was: Andy Taylor)


this is probably because the as7 code is ignoring the durable flag
                
> Persistent messages sent to JMS destinations deployed via a war file do not recover after a crash
> -------------------------------------------------------------------------------------------------
>
>                 Key: AS7-4203
>                 URL: https://issues.jboss.org/browse/AS7-4203
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 7.1.2.Final
>            Reporter: Michael Musgrove
>            Assignee: Jeff Mesnil
>
> I came across this issue whilst testing XA. The test case does a JPA update followed by JMS send inside a transaction. I allow both resources to prepare, I allow the JPA resource to commit but crash the AS (via Byteman) just before committing the JMS resource.
> If I define the queue in standalone-full.xml then the JMS message is delivered when recovery kicks in (ie after restarting the server). However, if I define the queue in the WEB-INF directory then the message is not recovered. The contents of hornetq-jms.xml that I ship with the war are:
> <?xml version="1.0" encoding="UTF-8"?>
> <messaging-deployment xmlns="urn:jboss:messaging-deployment:1.0">
>     <hornetq-server>
>         <jms-destinations>
>             <jms-queue name="jtaXaTestQueue">
>                 <entry name="queue/jtaXaTest"/>
>                 <entry name="java:jboss/exported/jms/queue/jtaXaTest"/>
>                 <durable>true</durable>
>             </jms-queue>
>         </jms-destinations>
>     </hornetq-server>
> </messaging-deployment>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira