[
https://issues.apache.org/jira/browse/AMQ-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101547#comment-16101547
]
ASF subversion and git services commented on AMQ-6778:
------------------------------------------------------
Commit 206f77adac24414751509195fd3b985d976573fd in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=206f77a ]
[AMQ-6778] - fix test regression that needs to account for presence of correct
advisory dests
> 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.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)
