You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2017/04/18 13:28:41 UTC

[jira] [Resolved] (QPID-7743) [Java Broker] Propagate current IO thread when switching protocol engine

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

Alex Rudyy resolved QPID-7743.
------------------------------
    Resolution: Fixed

The change look good to me

> [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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org