activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Lichtin (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3519) Allow getJMSRedelivered flag to survive a restart
Date Wed, 30 Nov 2011 20:43:40 GMT

    [ https://issues.apache.org/jira/browse/AMQ-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160315#comment-13160315
] 

Martin Lichtin commented on AMQ-3519:
-------------------------------------

Gary, is this feature for KahaDB only or will it also work for JDBC persistence adapter?
                
> Allow getJMSRedelivered flag to survive a restart
> -------------------------------------------------
>
>                 Key: AMQ-3519
>                 URL: https://issues.apache.org/jira/browse/AMQ-3519
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: jms, redelivery, reliable
>             Fix For: 5.6.0
>
>
> Jmsredelivery status is maintained by the activemq consumer and in memory by the broker
when a consumer closes. If the broker is restarted, the redelivery status is lost.
> The broker never rewrites a message so the modified property is lost.
> To make the redelivery flag reliable, it needs to be persisted.

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

        

Mime
View raw message