[
https://issues.apache.org/jira/browse/ARTEMIS-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100129#comment-17100129
]
Robbie Gemmell commented on ARTEMIS-2751:
-----------------------------------------
And no, I dont know the exceptions that were being caused, the Jira annoyingly
omits the useful detail like that. That said, I have a vague recollection it
was perhaps from the above stated immutability actually being enforced at the
time and entirely preventing messages being sent when the toggle was enabled.
> Call to AMQPMessage.setValidatedUserID does nothing
> ---------------------------------------------------
>
> Key: ARTEMIS-2751
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2751
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.12.0
> Reporter: Viktor Kolomeyko
> Priority: Major
>
> Method {{setValidatedUserID}} is not overridden for {{AMQPMessage}} class -
> therefore it calls parent implementation which does nothing.
> On the other hand:
> {{org.apache.activemq.artemis.core.message.impl.CoreMessage#setValidatedUserID}}
> does the right thing and correctly retains validated user information as
> supplied by
> {{org.apache.activemq.artemis.core.server.impl.ServerSessionImpl#doSend}}
> This deficiency prevents from reading
> {{org.apache.activemq.artemis.api.core.Message#HDR_VALIDATED_USER}} attribute
> when it is received via AMQP protocol.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
