You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2013/09/10 17:08:53 UTC
[jira] [Commented] (AMQ-4717) populateJMSXUserID is not setting the
JMSXUserID property on the JMS message in JMX
[ https://issues.apache.org/jira/browse/AMQ-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763100#comment-13763100 ]
Hiram Chirino commented on AMQ-4717:
------------------------------------
The JMSXUserID was being set in the message but just not showing up when browsed via JMX. I've applied fix so that JMSXUserID shows up in JMX too.
> 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
>
> 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