[ 
https://issues.apache.org/jira/browse/ARTEMIS-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985492#comment-15985492
 ] 

ASF subversion and git services commented on ARTEMIS-1112:
----------------------------------------------------------

Commit 2f175b8d4ef00fe3b9a6388cc4beab7fa22461c1 in activemq-artemis's branch 
refs/heads/master from [~bgutjahr]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=2f175b8 ]

 ARTEMIS-1112: don't block live activation if another live server is running

Instead of going directly into backup mode within the shared-store
live activation, we just change the HA-policy to slave and return
to the caller - ActiveMQServerImpl.internalStart().
The caller will then handle the backup activation as usual
in a separate thread, such that EmbeddedJMS.start() can return.

Also added a related integration test.


> 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
>
> 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)

Reply via email to