Failover issues were due to inability to take the lock on the filesystem.
Moving to an external NFSv4 solved the problem.
Unfortunately, from logs this is not immediate. Actually, the backup server
says that it acquires the backup lock even if this is not true.
Thanks for help.
--
Sent from:
Hi all,
I first tried with Artemis 2.7.0 but I didn't make it, now I'm trying with
Artemis 2.9.0, still looking for some luck.
What I want to achieve is a basic shared storage master/slave cluster with
static discovery.
I have a java client that connects to the master. Java code is provided
be
I moved to Artemis 2.9.0 so probably it would be better to open a new thread.
Thanks,
Lorenzo
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi,
some changes.
The first issue that I figured out on my broker.xml files was the leading
"/" on all file locations. This was preventing the slave to share the same
storage as the master.
Then I moved to 2.9.0. But I'm still experiencing weird behaviour.
The client application connects rand
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
Apologies! Preview was working but... don't know what happened.
Java client application exception:
Caught exception! javax.jms.JMSException: AMQ219014: Timed out after waiting
30,000 ms for response when sending packet 71
javax.jms.JMSException: AMQ219014: Timed out after waiting 30,000 ms for
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
sys
