You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2008/12/10 01:32:05 UTC

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

non-amq messages don't get JMS* header properties set on them when sent.
------------------------------------------------------------------------

                 Key: AMQ-2029
                 URL: https://issues.apache.org/activemq/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.

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

Posted by "David Jencks (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/activemq/browse/AMQ-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed AMQ-2029.
-----------------------------

    Resolution: Fixed

Rev 725019.  Set the properties on the message before transforming it to an amq message.  Add some tests to make sure they are present after sending.

> non-amq messages don't get JMS* header properties set on them when sent.
> ------------------------------------------------------------------------
>
>                 Key: AMQ-2029
>                 URL: https://issues.apache.org/activemq/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.