[
https://issues.apache.org/jira/browse/ARTEMIS-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163198#comment-16163198
]
Gary Tully commented on ARTEMIS-1417:
-------------------------------------
There may be some inspiration in 5.x - we have taken to writing to the lockfile
to ensure it has not been deleted and recreated.
see some history at:
https://github.com/apache/activemq/commits/57795bafcea290c6879bb288822435c480a9212d/activemq-broker/src/main/java/org/apache/activemq/util/LockFile.java
> Failback not working on NFSv4
> -----------------------------
>
> Key: ARTEMIS-1417
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1417
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.3.0
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Fix For: 2.4.0
>
>
> If Artemis is using NFSv4 as shared store for its messaging journal to
> provide HA then a write to server.lock made by one server may not be
> propagated to the other server. This prevents failback from happening. This
> is change in behavior in data synchronization between two NFSv4 clients was
> observed when recently upgrading Linux platforms.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
