[
https://issues.apache.org/jira/browse/ARTEMIS-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Nigro updated ARTEMIS-1876:
-------------------------------------
Description:
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.
was:
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 and is not production-ready.
It is causing several regressions with Oracle on the test suite.
> 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)
