Details
-
New Feature
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
5.0.2
-
None
-
None
-
1
-
Platform 168, Platform 169
Description
The is a combined backport of REPO-1811, REPO-1873, REPO-1874 and REPO-1875.
I'll merge/squash all those changes into a single commit, except those applying to the new (12.0) ConfigurationManagement feature. The latter (2) commits I'll squash in a separate/second commit.
The reason for squashing and collapsing all these commits is to make it easier to backport these changes to 11.2 and 10.2 (except the one/separate commit concerning the ConfigurationManagement).
Any future rework/fixes on 12.0, 11.2 or 10.2 touching upon these changes might want/need to review the original commits and their commit messages on the 12.1/master branch instead!
Attachments
Issue Links
- causes
-
REPO-1917 [Backport 12.0] LockManager usage issue in clustered environment
- Closed
- is a backport of
-
REPO-1875 The new LockManager must support MsSQL as backing databases
- Closed
-
REPO-1811 Implement local in memory (JVM) and persisted DB Lock Service
- Closed
-
REPO-1873 Support closing of a LockResource by a different thread
- Closed
-
REPO-1874 Leverage LockManager for the RepositoryScheduler replacing the deprecated HippoLock usage
- Closed
- relates to
-
REPO-1915 LockManager usage issue in clustered environment
- Closed