[
https://issues.apache.org/jira/browse/AMQ-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941764#comment-13941764
]
Gary Tully edited comment on AMQ-4886 at 3/20/14 2:16 PM:
----------------------------------------------------------
the deadlock on shutdown is resolved in
http://git-wip-us.apache.org/repos/asf/activemq/commit/cb6941ee
lets see how this fares before closing - to ensure there are no other issues.
was (Author: gtully):
the deadlock on shutdown is resolved in
http://git-wip-us.apache.org/repos/asf/activemq/commit/cb6941ee
lest see how this fairs before closing - to ensure there are no other issues.
> AMQ2149LevelDBTest hangs or fails frequently
> --------------------------------------------
>
> Key: AMQ-4886
> URL: https://issues.apache.org/jira/browse/AMQ-4886
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Kevin Earls
> Assignee: Kevin Earls
> Attachments: AMQ2149LevelDBTest.stack
>
>
> I'll update this as I get more information, but this test suite has multiple
> cases that hang and timeout frequently
> (testTopicTransactionalOrderWithRestart and testTopicOrderWithRestart seem to
> do so most frequently.)
> It can also hang in tearDown, which causes the whole suite to hang without
> timing out, which can be a problem when run under Hudson or Jenkins.
> I will attach a stack trace of the tearDown hang, and also update
> AMQ2149Test to prevent this. I'm also going to update the test to use JUnit4
> and reduce the timeouts from 30 to 5 minutes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
