Details
-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
Description
Improve timeouts in AS TS
- JMSMessageDrivenBeanTestCase should use TimeoutUtil for timeout
- increase timeout in PassivationTestCase
- JspCompilerTestCase should use TimeoutUtil for timeout
- increase timeout in MDBTestCase
- increase the default forked process timeout for basic module to hour, same timeout is used in clustering module
- remove usage of TimeoutUtil from TxTestUtil. If -Dts.timeout.factor=200 is used, MessageDrivenTimeoutTestCase.transactionTimeoutAnnotation and MessageDrivenTimeoutTestCase.transactionTimeoutActivationProperty fail:
java.lang.AssertionError: Sent and received message does not match at expected way expected:<replying annotation timeout> but was:<null> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.jboss.as.test.integration.ejb.transaction.mdb.timeout.MessageDrivenTimeoutTestCase.transactionTimeoutAnnotation(MessageDrivenTimeoutTestCase.java:109) java.lang.AssertionError: No message should be received as mdb timeouted expected null, but was:<replying annotation timeout> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotNull(Assert.java:755) at org.junit.Assert.assertNull(Assert.java:737) at org.jboss.as.test.integration.ejb.transaction.mdb.timeout.MessageDrivenTimeoutTestCase.transactionTimeoutActivationProperty(MessageDrivenTimeoutTestCase.java:126)
This stabilizes TS on slower machines.
Attachments
Issue Links
- clones
-
JBEAP-8966 Improve timeouts in AS TS
- Verified