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 On Wed, Jun 5, 2019 at 10:58 AM hannibal <hanniba...@gmail.com> wrote: > Hi all, > I'm trying to setup a simple master/slave cluster with shared store. > > I have VMs with RHEL 7.6 running in virtual box VMs with vagrant, Artemis > 2.7.0. > The shared storage is provided by vagrant. Host OS is Win 10. > > From logs, it seems that the master is acquiring the lock on the file > system. Clearly there is a WARN on master server that an error happened but > it's really not clear to me what's the meaning of such error. Also because > the very same log says that a connection from master to slave was created. > The console of the master allows me to see everything while the console of > the second only allows me to see the cluster connections. > > Then, I start sending messages from a separate java application hosted by > the host. > While producing and consuming messages, if I kill the master, the client > application times out . > > > > Logging in again on consoles, of course console of the master is not > available, slave console still doesn't allow me to see anything else than > connections. > > I was used to ActiveMQ 5.x which, as I remember, was handling the failover > seamlessly. > > So, I'm doing something wrong for sure but I can't get what. Could you > please help me figuring this out? > > Here the conf of the first broker: artemis-1M > > > > Here the conf of the second broker: artemis-1S > > > > This is the log of the first node: > > > > > This is the log of the second node: > > > > Here where the client application creates connections. > > > > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
