[
https://issues.apache.org/activemq/browse/AMQ-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61301#action_61301
]
Kevan Miller commented on AMQ-2840:
-----------------------------------
In Geronimo, we've been lining up our next 2.2.x release to be based on 5.4.0.
With the limited time between this regression and release, we weren't able to
nail down the cause of this problem (we had made connector/transaction manager
updates around the same time, which could have had some impact on our JMS
tests).
So, I, for one, would be interested in a 5.4.1 release "soon".
> JMSX Properties not returned from message.propertyExists() and
> message.getPropertyNames()
> -----------------------------------------------------------------------------------------
>
> Key: AMQ-2840
> URL: https://issues.apache.org/activemq/browse/AMQ-2840
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.0
> Reporter: Andriy Hnativ
> Assignee: Gary Tully
> Fix For: 5.4.1
>
> Attachments: patch.txt
>
>
> Methods propertyExists() and getPropertyNames() defined in the class
> org.apache.activemq.command.ActiveMQMessage (activemq-core) return only
> custom properties. The JMSX properties (like JMSXDeliveryCount) are not being
> returned. This problem exists not only for a new version of ActiveMQ (5.4),
> but also for 5.3 (and probably for others as well).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
