Fix for unit tests that are causing build failures in certain environments

This commit is contained in:
Mark Payne 2018-02-07 14:13:06 -05:00
parent 2b062e211f
commit d7da04209a
2 changed files with 3 additions and 4 deletions

View File

@ -154,8 +154,7 @@ public class JMSPublisherConsumerTest {
}
}
@Test(timeout = 2000000)
@Test(timeout = 20000)
public void testMultipleThreads() throws Exception {
String destinationName = "testQueue";
JmsTemplate publishTemplate = CommonTest.buildJmsTemplateForDestination(false);

View File

@ -73,7 +73,7 @@ public class PublishJMSTest {
assertEquals("cooQueue", ((Queue) message.getJMSReplyTo()).getQueueName());
assertEquals("foo", message.getStringProperty("foo"));
runner.run(1, true); // Run once just so that we can trigger the shutdown of the Connection Factory
runner.run(1, true, false); // Run once just so that we can trigger the shutdown of the Connection Factory
}
@Test
@ -111,7 +111,7 @@ public class PublishJMSTest {
assertEquals("cooQueue", ((Queue) message.getJMSReplyTo()).getQueueName());
assertEquals("foo", message.getStringProperty("foo"));
runner.run(1, true); // Run once just so that we can trigger the shutdown of the Connection Factory
runner.run(1, true, false); // Run once just so that we can trigger the shutdown of the Connection Factory
}
@Test