[
https://issues.apache.org/jira/browse/ARTEMIS-4205?focusedWorklogId=867203&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867203
]
ASF GitHub Bot logged work on ARTEMIS-4205:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jun/23 16:37
Start Date: 23/Jun/23 16:37
Worklog Time Spent: 10m
Work Description: rvais commented on PR #4403:
URL:
https://github.com/apache/activemq-artemis/pull/4403#issuecomment-1604529631
@funkyjive would you agree that your implementation could be changed/updated
to work as an implementation of potential locking mechanism for the
jdbcSharedStateManager to leverage? What I, personally would like to see is
simplified and unified approach. What came to my mind when reading your PR was
that you could use the existing API for the locking mechanism, and just fill in
your approach to locks themselves.
Issue Time Tracking
-------------------
Worklog Id: (was: 867203)
Time Spent: 1h 40m (was: 1.5h)
> 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 40m
> 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)
