Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

ARTEMIS-1489 Adjusting timeouts on test 

The Critical analyzer is supposed to catch Deadlocks, and such
can only be resolved by killing the VM.

This test is using shutdown as it would be a bit more complex to
handle Byteman to then halt the VM. This will validate the
CriticalAnalyzer is capturing the event, and in such it would halt the VM.
This commit is contained in:
Clebert Suconic 2017-10-31 08:54:23 -04:00 committed by Justin Bertram
parent 2bf690e21b
commit f8a0eec2cf
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
tests/extra-tests/src/test/java/org/apache/activemq/artemis/tests/extras/byteman/CriticalAnalyzerFaultInjectionTest.java
View File

@ -17,6 +17,7 @@
package org.apache.activemq.artemis.tests.extras.byteman;
import javax.jms.DeliveryMode;
import javax.jms.JMSException;
import javax.jms.MessageProducer;
import javax.jms.Queue;
import javax.jms.Session;
@ -41,8 +42,8 @@ public class CriticalAnalyzerFaultInjectionTest extends JMSTestBase {
// Critical Analyzer Settings
private static long CHECK_PERIOD = 100;
private static long TIMEOUT = 3000;
public static long TEST_TIMEOUT = 60000;
private static long TIMEOUT = 1000;
public static long TEST_TIMEOUT = 5000;
private SimpleString address = SimpleString.toSimpleString("faultInjectionTestAddress");
@ -95,6 +96,7 @@ public class CriticalAnalyzerFaultInjectionTest extends JMSTestBase {
p.setDeliveryMode(DeliveryMode.PERSISTENT);
conn.start();
p.send(s.createTextMessage("payload"));
} catch (JMSException expected) {
} finally {
if (conn != null) {
conn.close();