Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1576
@clebertsuconic @mtaylor I'm already using prepared statements with
different parameters but each row id can have only one meaning (live lock,
backup lock,nodeId and state) hence it's better IMO to have a clear distinction
between them as it is now: you can't have more than 2 rows to hold locks and it
is the same with the other rows.
@clebertsuconic I've refactored the classes into a 'jdbc' package and I've
built an high level abstraction to manage the scheduling of the locks using a
common Artemis scheduled component implementation.
Right now most classes will be package private in order to prohibit any
other use until (if) the file based lock NodeManager will be refactored using
them.
---
