From b9334960e06f48454305fc60732b683347d4aaed Mon Sep 17 00:00:00 2001 From: Timothy Bish Date: Fri, 13 May 2016 12:50:13 -0400 Subject: [PATCH] Add some additional time to the wait for completion assert. On a sufficiently loaded system 30s is not quite enough. This is reproducable if run while a heavily I/O based application is also running in the background. --- .../test/java/org/apache/activemq/store/PListTestSupport.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/activemq-broker/src/test/java/org/apache/activemq/store/PListTestSupport.java b/activemq-broker/src/test/java/org/apache/activemq/store/PListTestSupport.java index 8fc7027ae6..152f96ac93 100644 --- a/activemq-broker/src/test/java/org/apache/activemq/store/PListTestSupport.java +++ b/activemq-broker/src/test/java/org/apache/activemq/store/PListTestSupport.java @@ -253,7 +253,7 @@ public abstract class PListTestSupport { synchronized (plistLocks(candidate)) { Object last = candidate.addLast(String.valueOf(i), payload); getFirst(candidate); - assertTrue(candidate.remove(last)); + assertTrue(candidate.remove(last)); } } } catch (Exception error) { @@ -273,7 +273,7 @@ public abstract class PListTestSupport { executor.execute(new B()); executor.shutdown(); - boolean finishedInTime = executor.awaitTermination(30, TimeUnit.SECONDS); + boolean finishedInTime = executor.awaitTermination(60, TimeUnit.SECONDS); assertTrue("no exceptions", exceptions.isEmpty()); assertTrue("finished ok", finishedInTime);