[
https://issues.apache.org/jira/browse/ARTEMIS-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474135#comment-16474135
]
Francesco Nigro commented on ARTEMIS-1865:
------------------------------------------
How the shared store pairs are configured? There are specific CIFS
configuration (timeout on connectivity etc etc) that should help on it,
similarly to NFS, but I'm not expert on both.
It looks to me like a problem of CIFS on locking file regions ie the master has
acquired the lock on the live region on the server.lock file and the CIFS
implementation is locking the entire file instead of a region, making the slave
not able to acquire lock on its backup region on the same file.
In any case if you have a reproducer would be simpler to search for a solution
instead of guess one :)
> Shared Store Cluster Doesn't Work on CIFS
> -----------------------------------------
>
> Key: ARTEMIS-1865
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1865
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.5.0
> Environment: RHEL 6.2
> Reporter: Ilkka Virolainen
> Priority: Minor
>
> When Artemis is configured as a shared store master/slave -pair with the
> journal saved on a CIFS share only the first instance is able to start. The
> instance started later will fail the acquire a lock to journal/server.lock
> file and will start in an invalid state. Similar shared store master/slave
> -configuration works correctly with 5.14.5.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
