[
https://issues.apache.org/jira/browse/ARTEMIS-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990812#comment-15990812
]
ASF GitHub Bot commented on ARTEMIS-1112:
-----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/1204
I will really need to revert this.
You would need a new option for this new behaviour...
When you have multiple Live server starting, the expected semantic is they
waiting the previous live to shutdown before they can get live.
As a backup, the backup will announce itself and failback would kick in.
This is breaking failback for good, and now allowing the previous semantic
in place. I have no other option beyond revert this.
if you want this new behaviour, you will need an option, proper
documentation and clear how this would behave. I have no idea how it would be
consistent with everything else yet, but we could discuss.
> EmbeddedJMS.start() doesn't return if shared-store master starts as backup
> server
> ---------------------------------------------------------------------------------
>
> Key: ARTEMIS-1112
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1112
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.5.4, 2.0.0
> Reporter: Bernd Gutjahr
> Priority: Minor
> Fix For: 2.next
>
>
> EmbeddedServer.start() doesn't return when a share-store master server has
> been configured, but at startup another server is already running as live
> server (i.e. another previously started master).
> In that case, this server becomes a backup server for the currently running
> live server. The start() method hangs until the currently running live server
> stops and this server actually becomes the new live server.
> This is inconsistent with starting a server as slave server, where the start
> method returns and doesn't wait until the slave took over as live server.
> It also blocks the application that called EmbeddedServer.start() to proceed
> it's normal operation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
