You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Kevin Earls (JIRA)" <ji...@apache.org> on 2013/03/28 19:19:15 UTC
[jira] [Updated] (AMQ-4415) AMQ2584Test, AMQ2870Test, and several
others hang or fail on some platforms when using LevelDB
[ https://issues.apache.org/jira/browse/AMQ-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Earls updated AMQ-4415:
-----------------------------
Attachment: AMQ-4415.patch
> AMQ2584Test, AMQ2870Test, and several others hang or fail on some platforms when using LevelDB
> ----------------------------------------------------------------------------------------------
>
> Key: AMQ-4415
> URL: https://issues.apache.org/jira/browse/AMQ-4415
> Project: ActiveMQ
> Issue Type: Bug
> Components: Test Cases
> Environment: AIX and Solaris
> Reporter: Kevin Earls
> Attachments: AMQ-4415.patch
>
>
> Problem tests include:
> AMQ2584Test
> AMQ2870Test
> QueueMbeanRestartTest
> FailoverTransactionTest
> ConcurrentProducerDurableConsumerTest
> DurableSubscriptionOfflineTest
> The patch adds timeouts, and for the AMQ2584Test and AMQ2870Test does not run the LevelDB instance of the test, as these fail in tearDown, so timeouts do not prevent the tests from hanging.
> Note: Where possible I've changed these from using CombinationTestSupport to JUnit4 Parameterized tests with timeouts defined. It looks like sometimes if a test which extends CombinationTestSupport turns on AutoFail and a timeout occurs, Maven reports the following:
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira