tidy up close for vm broker - seems ci failure of InMemeoryJmsSchedulerTest is related to overlap between tests of vm transport

This commit is contained in:
gtully 2016-05-25 12:34:07 +01:00
parent fe9d99e7a0
commit 281fbb1f9d
1 changed files with 6 additions and 0 deletions

View File

@ -84,6 +84,7 @@ public class JmsSchedulerTest extends JobSchedulerTestSupport {
assertEquals(1, list.size());
latch.await(240, TimeUnit.SECONDS);
assertEquals(COUNT, count.get());
connection.close();
}
@Test
@ -117,6 +118,7 @@ public class JmsSchedulerTest extends JobSchedulerTestSupport {
assertEquals(latch.getCount(), COUNT);
latch.await(5, TimeUnit.SECONDS);
assertEquals(latch.getCount(), 0);
connection.close();
}
@Test
@ -156,6 +158,7 @@ public class JmsSchedulerTest extends JobSchedulerTestSupport {
assertEquals(latch.getCount(), COUNT);
latch.await(5, TimeUnit.SECONDS);
assertEquals(latch.getCount(), 0);
connection.close();
}
@Test
@ -193,6 +196,7 @@ public class JmsSchedulerTest extends JobSchedulerTestSupport {
// wait a little longer - make sure we only get NUMBER of replays
Thread.sleep(1000);
assertEquals(NUMBER, count.get());
connection.close();
}
@Test
@ -230,6 +234,7 @@ public class JmsSchedulerTest extends JobSchedulerTestSupport {
message.setLongProperty(ScheduledMessage.AMQ_SCHEDULED_DELAY, time);
producer.send(message);
producer.close();
connection.close();
}
@Test
@ -290,5 +295,6 @@ public class JmsSchedulerTest extends JobSchedulerTestSupport {
latch.await(20000l, TimeUnit.MILLISECONDS);
assertEquals("Consumer did not receive all messages.", 0, latch.getCount());
conn.close();
}
}