activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-4717) populateJMSXUserID is not setting the JMSXUserID property on the JMS message in JMX
Date Tue, 10 Sep 2013 16:56:54 GMT

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

Hiram Chirino updated AMQ-4717:
-------------------------------

    Issue Type: Bug  (was: New Feature)
    
> populateJMSXUserID is not setting the JMSXUserID property on the JMS message in JMX
> -----------------------------------------------------------------------------------
>
>                 Key: AMQ-4717
>                 URL: https://issues.apache.org/jira/browse/AMQ-4717
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.5.1, 5.6.0, 5.8.0
>         Environment: OSX
> java version "1.7.0_25"
>            Reporter: Jason Sherman
>            Assignee: Hiram Chirino
>              Labels: authentication
>             Fix For: 5.9.0
>
>
> When setting the attribute populateJMSXUserID="true" as documented [1] the broker should
populate the JMS message with the JMSXUserID property.  However, this is not the case.  
> I have configured the broker to require authentication and sent a message to a Queue
using the JMS producer shipped with the distribution.  The message is then inspected via JMX
and the JMSXUserID property is not set.
> [1] http://activemq.apache.org/jmsxuserid.html

--
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

Mime
View raw message