[
https://issues.apache.org/jira/browse/QPID-7600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782960#comment-15782960
]
Keith Wall commented on QPID-7600:
----------------------------------
The AMQManagementTest was failing on the 0-8..0-91 path since r1776037.
Previously the enqueue onto the ManagementNode was always performed by the
'AMQChannel#deliverCurrentMessageIfComplete' execution path. r1776037
refactored the ManagementNode with the result that the enqueue was performed by
the {{AMQChannel#receivedComplete}} path.
{{ManagementNode#getResponseDestination}} relies on the SessionPrincipal being
available in the thread's running subject. Owing to the defect described
above, the session principal is not available, so the management responses fail
to route to the special '!response' address.
> AMQChannel#receivedComplete is performed without the SessionPrincipal within
> the thread access controller context
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7600
> URL: https://issues.apache.org/jira/browse/QPID-7600
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-7.0.0
>
>
> By design, threads working on behalf of the channel are supposed to carry the
> SessionPrincipal as part of the running subject. If the channel is
> processing on a frame, the principal is made available by
> {{BrokerDecoder#processAMQPFrames}}, however, if the channel is performing
> 'post-work' (i.e. {{AMQChannel#receivedComplete}}) it currently forgets to
> make the principal available.
> As exposed by test failures since r1776037 (QPID-6028),
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
