[jboss-jira] [JBoss JIRA] Closed: (JBAS-4870) Redelivery flags not updated in case of JBossMQ node failure

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4870?page=all ]

Adrian Brock closed JBAS-4870.
------------------------------

    Resolution: Done

This has been fixed.

Since this is a corner case and the fix means we have to update all persistent messages
in the database before delivering the message (i.e. whether the message gets redelivered or not)
I've added an option to the destination manager so it can be reverted to the old behaviour.

<!-- Only update redelivery status of a persistent message in the database when a NACK is received -->
<attribute name="LazyRedeliveryUpdate">true</attribute>

The default is false.

> Redelivery flags not updated in case of JBossMQ node failure
> ------------------------------------------------------------
>
>                 Key: JBAS-4870
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4870
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>         Attachments: testredelivery.zip
>
>
> When the JBossMQ node fails with messages currently being delivered to the clients,
> the redelivery status is not updated after the node is recovered (either locally or on a different for HAJMS).
> The issue is that the redelivery status (in the database) is not updated until the server receives the NACK
> (which it won't do if it has crashed).
> A potential fix, is to update the status early before delivering the message to the client,
> see the forum thread for more detail.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira