[
https://issues.apache.org/jira/browse/ARTEMIS-4205?focusedWorklogId=867244&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867244
]
ASF GitHub Bot logged work on ARTEMIS-4205:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jun/23 17:47
Start Date: 24/Jun/23 17:47
Worklog Time Spent: 10m
Work Description: funkyjive commented on PR #4403:
URL:
https://github.com/apache/activemq-artemis/pull/4403#issuecomment-1605667258
@rvais Truth is I don't know if I really do agree with that. I coded an
implementation oriented around of the DistributedPrimitiveManager
specification using specialized database features.
I don't know that attempting to utilize those features and approaches inside
JdbcSharedStateManager ultimately does create something "simplified and
unified". Those underlying mechanisms are actually quite different from
anything in JdbcSharedStateManager. For instance, go look at any method in
JdbcSharedStateManager
Issue Time Tracking
-------------------
Worklog Id: (was: 867244)
Time Spent: 1h 50m (was: 1h 40m)
> Allow a database to be used to meet pluggable quorum vote locking requirements
> ------------------------------------------------------------------------------
>
> Key: ARTEMIS-4205
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4205
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Reporter: David Bennion
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Utilizing the new pluggable quorum vote locking api, implement the locking
> manager using a JDBC database connection. Support for Oracle, MSSQL and
> Postgres is included initially, with H2 being utilized for unit testing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
