It may work as expected, but to my knowledge it's never been tested so it may not. The NullPointerException you're seeing the master's log file is more concerning than anything. I'm not sure why that would happen.
Can you reproduce this on 2.9.0 [1]? I'm in the process of releasing 2.9.0 now. The binary download is available, but I haven't updated the website yet. Justin [1] https://dist.apache.org/repos/dist/release/activemq/activemq-artemis/2.9.0/ On Fri, Jun 7, 2019 at 4:18 AM hannibal <hanniba...@gmail.com> wrote: > Hi Justin, > I added all missing parts. > Regarding FS lock, if logs are trustworthy, I can see on the master node: > 2019-06-05 08:35:47,492 INFO [org.apache.activemq.artemis.core.server] > AMQ221035: Live Server Obtained live lock > So I'm assuming the lock is working. > > On slave I can see: > 2019-06-05 08:35:57,601 INFO [org.apache.activemq.artemis.core.server] > AMQ221033: ** got backup lock > > Can I think that it's working as expected? > > > jbertram wrote > > It looks like everything you pasted didn't make it through so there's no > > configuration, logging, or client details. Therefore, it's hard to offer > > much help. > > > > You say that the "shared storage is provided by vagrant." I'm not > familiar > > with vagrant. Does it support file or file-region locking so that locks > > held by one process are visible to other processes across the share? If > > not, it won't be suitable for Artemis master/slave shared storage. > > > > > > Justin > > > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
