[ 
https://issues.apache.org/jira/browse/QPID-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982769#comment-15982769
 ] 

ASF subversion and git services commented on QPID-7743:
-------------------------------------------------------

Commit 8a3931d7f6cb1eafbc5740b2073dd9777314c9e9 in qpid-broker-j's branch 
refs/heads/6.1.x from [~lorenz.quack]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=8a3931d ]

QPID-7743: [Java Broker] Propagate current IO thread when switching protocol 
engine


> [Java Broker] Propagate current IO thread when switching protocol engine
> ------------------------------------------------------------------------
>
>                 Key: QPID-7743
>                 URL: https://issues.apache.org/jira/browse/QPID-7743
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Lorenz Quack
>             Fix For: qpid-java-broker-7.0.0
>
>
> The {{ProtocolEngine}} needs to know the current IO Thread and this is 
> communicated via {{ProtocolEngine#setIOThread}}.
> Before protocol negotiation the {{MultiVersionProtocolEngine}} uses a 
> {{SelfDelegateProtocolEngine}}. When the protocol negotiation completes the 
> {{MultiVersionProtocolEngine}} switches to the appropriate implementation. 
> However it does currently not communicate the current IO Thread to this new 
> engine. Only after the next call to {{ProtocolEngine#setIOThread}} will the 
> correct IO Thread be set on the new engine.
> When switching engine the correct IO Thread should be communicated 
> immediately. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to