[
https://issues.apache.org/jira/browse/ARTEMIS-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483751#comment-16483751
]
ASF subversion and git services commented on ARTEMIS-1876:
----------------------------------------------------------
Commit 6b5f9d943c37e169e4b5b7b14914bfde2fa38c5b in activemq-artemis's branch
refs/heads/1.x from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=6b5f9d9 ]
ARTEMIS-1876 InVMNodeManager shouldn't be used if no JDBC HA is configured
When database persistence and no shared store option is being used,
Artemis is choosing to use InVMNodeManager, that is not providing
the same behaviour of FileLockNodeManager.
(cherry picked from commit f886c0bdb451c947143fba6cf07cbf8ce7f3ff4d)
> InVMNodeManager shouldn't be used if no JDBC HA is configured
> -------------------------------------------------------------
>
> Key: ARTEMIS-1876
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1876
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.6.0
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Fix For: 2.7.0
>
>
> When database persistence and no shared store option is being used, Artemis
> is choosing to use InVMNodeManager, that is not providing the same behaviour
> of FileLockNodeManager.
> It is causing several regressions with Oracle on the test suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
