[
https://issues.apache.org/activemq/browse/AMQ-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58827#action_58827
]
Gary Tully commented on AMQ-1111:
---------------------------------
To resolve this, the message needs to get stored twice or on each redelivery
attempt. currently the redelivery state is maintained only in memory. It is
unlikely that this issue will be resolved in the short term because the stores
would need to accept duplicates or updates which they are not designed for.
> Message.getJMSRedelivered() does not work if the server restarts
> ----------------------------------------------------------------
>
> Key: AMQ-1111
> URL: https://issues.apache.org/activemq/browse/AMQ-1111
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.0.2
> Environment: Active MQ 4.0.2
> Reporter: r-a-v-i
> Fix For: 4.1.3
>
>
> Steps to reproduce :
> a) Start ActiveMQ 4.0.2
> b) Create a transacted session, create a topic , publish a message to the
> topic.
> c) Create a durable subscriber and kill the durable subscriber, before the
> session.commit() is called.
> (Put a debug break point just before the session.commit())
> e) Message gets redelivered and in the onMessage() method of the respective
> listener Message.getJMSRedelivered() become true.
> In the above use case, instead of killing the durable subscriber, if I
> restart the server, the message is getting redelivered but
> Message.getJMSRedelivered() is false.
>
> Please contact me if you need more details.
> Thanks,
> r-a-v-i
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
