Github user bgutjahr commented on the issue:
https://github.com/apache/activemq-artemis/pull/1204
In the meantime, I have found a way to get what I want without changing
Artemis code. Not very nice, but seems to work: when I start a slave server, it
automatically becomes live when there is not live running. There is only one
exception: on first startup when no live has even been started, the slave waits
for a live server to start before going into backup mode. But in that case, the
is no bindings directory. So my solution is to check for the existance of a
bindings directory and start a master server if it is missing. It becomes live
and creates the bindings directory. From then on, I always start slave servers.
This means I won't need an Artemis enhancement. Personally, I would prefer
that the start() method doesn't block infinitely. I.e. start of a master server
should return even if the master becomes a backup; and start of a slave server
should also become live even if no live server has even run before. Even
throwing an exception instead instead of blocking would be better in my
opinion).
But since than behavior can't be changed due without breaking backwards
compatibility, I'll just use my own solution and check for the bindings
directory.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
