[
https://issues.apache.org/jira/browse/ARTEMIS-4205?focusedWorklogId=865577&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-865577
]
ASF GitHub Bot logged work on ARTEMIS-4205:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jun/23 16:56
Start Date: 14/Jun/23 16:56
Worklog Time Spent: 10m
Work Description: funkyjive commented on PR #4403:
URL:
https://github.com/apache/activemq-artemis/pull/4403#issuecomment-1591655010
Full disclosure, I don't know each detail about the inner functioning of the
JdbcSharedStateManager itself. So there may be things that I am missing.
But high level differences between the approach:
The JdbcSharedStateManager is written to utilize a locking mechanism more
closely to the JDBC Spec
Issue Time Tracking
-------------------
Worklog Id: (was: 865577)
Time Spent: 1.5h (was: 1h 20m)
> 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: 1.5h
> 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)
