[
https://issues.apache.org/jira/browse/TUBEMQ-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guocheng Zhang resolved TUBEMQ-158.
-----------------------------------
Fix Version/s: 0.5.0
Resolution: Fixed
> nextWithAuthInfo2B status should be managed independently according to Broker
> -----------------------------------------------------------------------------
>
> Key: TUBEMQ-158
> URL: https://issues.apache.org/jira/browse/TUBEMQ-158
> Project: Apache TubeMQ
> Issue Type: Bug
> Reporter: Guocheng Zhang
> Assignee: Guocheng Zhang
> Priority: Normal
> Labels: pull-request-available
> Fix For: 0.5.0
>
> Attachments: image-2020-05-26-20-06-46-124.png
>
>
> In class BaseMessageConsumer.java , the nextWithAuthInfo2B parameter is set
> globally, but its purpose is to record whether the contacted Broker will
> perform authentication and authorization management during the next
> interaction. This parameter should be managed separately according to the
> Broker dimension:
> !image-2020-05-26-20-06-46-124.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
