You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2011/08/25 12:12:29 UTC
[jira] [Commented] (QPID-3432) Test SyncWaitTimeoutDelayTest fails
[ https://issues.apache.org/jira/browse/QPID-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090904#comment-13090904 ]
Keith Wall commented on QPID-3432:
----------------------------------
These tests exercise a 0-8..0-9-1 specific system property (amqj.default_syncwrite_timeout) and should therefore be excluded from the 0-10 profile.
0-10 should offer the ability to control the transaction timeout (now the subject of QPID-3449). When it does I think it would make sense to refactor these tests to test this ability for all profiles.
> Test SyncWaitTimeoutDelayTest fails
> -----------------------------------
>
> Key: QPID-3432
> URL: https://issues.apache.org/jira/browse/QPID-3432
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Reporter: Alex Rudyy
> Priority: Minor
>
> The test fails with the following stack trace:
> Commit occured even though syncWait timeout is shorter than delay in commit
> junit.framework.AssertionFailedError: Commit occured even though syncWait timeout is shorter than delay in commit
> at org.apache.qpid.test.client.timeouts.SyncWaitTimeoutDelayTest.test(SyncWaitTimeoutDelayTest.java:61)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org