We could not find a solution within two days and switched finally to
replication as HA strategy.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
In terms of shared-storage there's really not much to configure. You
simply point both nodes at the same journal. I don't see how this issue
could be caused by a faulty configuration, especially given that you see
the problem outside of Artemis as well when simply using 'cat'.
Justin
On Tue,
Could a faulty cluster configuration lead to this problem?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
The Bugzilla you cited is related to the problem I mentioned previously
that Artemis had regarding the locking. I really have no idea why your
particular problem only manifests on 7.4 vs 7.3. That would probably need
to be addressed by an expert in the NFS community.
Justin
On Mon, Nov 13,
Might the problem has a correlation to this issue
https://bugzilla.redhat.com/show_bug.cgi?id=1486132? I'm just wondering why
it works on RHEL 7.3 but not on 7.4?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
You are right. I installed Artemis 2.4.0 on the same Host like EAP 7.0 is
installed and it worked as expected. Means the problem is not on the
broker-side. The only difference is the Linux Version (RHEL 7.3 vs. 7.4).
Anyway, I will post a replay when we have found the problem.
--
Sent from:
It should work, but like you said will be slow. Artemis 2.4.0 had a change
in the way it handles the lock file for the NFSv4 use-case [1], but the
code throwing the exception you're seeing wasn't touched. In fact, that
bit of code hasn't had any semantic changes in years (just some style
We have a HA setup with shared storage on a NFSv4 share. During the startup
of the second server I got the following Exception and the startup process
will be stopped:
17:32:12,900 INFO [org.apache.activemq.artemis.integration.bootstrap]
AMQ101000: Starting ActiveMQ Artemis Server
Exception in
