[jira] Commented: (AMQ-2029) non-amq messages don't get JMS* header properties set on them when sent.

["Gary Tully (JIRA)" <ji...@apache.org>]

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

Gary Tully commented on AMQ-2029:
---------------------------------

David, can you recall the use case for this change. Wonder if destination name, the format being provider dependent, is one of the necessary properties in your use case. see: AMQ-2963

> non-amq messages don't get JMS* header properties set on them when sent.
> ------------------------------------------------------------------------
>
>                 Key: AMQ-2029
>                 URL: https://issues.apache.org/jira/browse/AMQ-2029
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 5.3.0
>
>
> JMS 1.1 spec section 3.4.11 lists properties that should be set from sending a message:
> JMSDestination, JMSDeliveryMode, JMSExpiration, JMSPriority, JMSMessageID, JMSTimestamp and presumably JMSRedelivered.  These are getting set on the amq-message copy rather than the original message in ActiveMQSession.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.