You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/06/06 00:32:20 UTC
[jira] [Commented] (AMQ-4352) Expired message on the dlq miss
originalExpiration property
[ https://issues.apache.org/jira/browse/AMQ-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676436#comment-13676436 ]
Timothy Bish commented on AMQ-4352:
-----------------------------------
Can you retest against a 5.9 SNAPSHOT and confirm if this is still an issue, just testing here and it seems to be working now.
> Expired message on the dlq miss originalExpiration property
> -----------------------------------------------------------
>
> Key: AMQ-4352
> URL: https://issues.apache.org/jira/browse/AMQ-4352
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.x
> Reporter: SuoNayi
> Fix For: 5.9.0
>
> Attachments: AMQ4352.patch, AMQ4352Test.java
>
>
> When messages expire they are moved to the dead letter queue for retrospection.
> Expired messages have one originalExpiration property to indicate when it's expired, but we can not see the property via Web Console or using consumers to fetch them from the dlq.
> The unit test reproduces the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira