[
https://issues.apache.org/jira/browse/AMQ-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635275#comment-13635275
]
Timothy Bish commented on AMQ-4352:
-----------------------------------
The problem here is when the message arrives at the connection over the VM
transport its properties aren't marshaled so the original expiration property
gets filtered.
> 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: 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
