From 955476b2dd08a2d90413008c658b3dacba8f0899 Mon Sep 17 00:00:00 2001
From: boli <boli@localhost>
Date: Tue, 22 Apr 2008 22:33:23 +0000
Subject: [PATCH] Fixed an issue where deadlocks could occur in the LockManager when the server is in heavy add/mod load. An add operation takes a read lock on the parent DN and a write lock on the target DN in that order. However, mod operations first takes an write lock on the target DN then inadvertantly tries takes an read lock on the parent DN through the entryExists method. This could cause a deadlock in the following case with the fair ordering reentrant read write lock:
---
opends/tests/unit-tests-testng/src/server/org/opends/server/replication/DependencyTest.java | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/opends/tests/unit-tests-testng/src/server/org/opends/server/replication/DependencyTest.java b/opends/tests/unit-tests-testng/src/server/org/opends/server/replication/DependencyTest.java
index fe9ba41..60403dd 100644
--- a/opends/tests/unit-tests-testng/src/server/org/opends/server/replication/DependencyTest.java
+++ b/opends/tests/unit-tests-testng/src/server/org/opends/server/replication/DependencyTest.java
@@ -91,7 +91,7 @@
* all those entries is also correctly ordered.
*/
@SuppressWarnings("unchecked")
- @Test(enabled=false, groups="slow")
+ @Test(enabled=true, groups="slow")
public void addModDelDependencyTest() throws Exception
{
ReplicationServer replServer = null;
--
Gitblit v1.10.0