activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1112) EmbeddedJMS.start() doesn't return if shared-store master starts as backup server
Date Thu, 04 May 2017 15:19:04 GMT


ASF subversion and git services commented on ARTEMIS-1112:

Commit 88e629a7aeb9c3168fd704c32e8ee2aad756b41b in activemq-artemis's branch refs/heads/1.x
from [~bgutjahr]
[;h=88e629a ]

ARTEMIS-1112: Added wait-for-activation option to shared-store-master config

Added a wait-for-activation option to shared-store master HA policies.
This option is enabled by default to ensure unchanged server startup behavior.

If this option is enabled, ActiveMQServer.start() with a shared-store master server will not
before the server has been activated.
If this options is disabled, start() will return after a background activation thread has
been started.
The caller can use waitForActivation() to wait until server is activated, or just check the
current activation status.

(cherry picked from commit 6017e305d90664b4bf5b8f891e43514907df9a4b)
(cherry picked from commit 7aa50546b3dc6c012bd7d4118d82055ffd1e1226)

> EmbeddedJMS.start() doesn't return if shared-store master starts as backup server
> ---------------------------------------------------------------------------------
>                 Key: ARTEMIS-1112
>                 URL:
>             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
> 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

This message was sent by Atlassian JIRA

View raw message