[jira] [Updated] (AMQ-6778) Advisories are dropped till broker is fully started in error

["Timothy Bish (JIRA)" <ji...@apache.org>]

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

Timothy Bish updated AMQ-6778:
------------------------------
    Fix Version/s: 5.15.1

> Advisories are dropped till broker is fully started in error
> ------------------------------------------------------------
>
>                 Key: AMQ-6778
>                 URL: https://issues.apache.org/jira/browse/AMQ-6778
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, networkbridge
>    Affects Versions: 5.15.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.15.1, 5.16.0
>
>
> The Advisory broker fire is conditional on the broker being fully started. This has been present for the longest time however the started flag has been modified to include a countDownLatch that is triggered on start completion.
> This means that consumers that connect to the active transportConnectors do not result in advisories which can mean incoming networkConnectors can mis this advise in error which results in the demand being ignored.
> From what I can see, the check for started does not add value and in the event of a failure to fire an advisory the error will be caught and logged rather than being ignored as it is now.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)