[ https://issues.apache.org/jira/browse/BOOKKEEPER-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546145#comment-13546145 ]
Sijie Guo commented on BOOKKEEPER-533: -------------------------------------- suspending delivery manager is to simulate the case that closesub finished later than subscriber, which is the problem before fixing BOOKKEEPER-507. another question, if Thread.suspend is not suggested to be used, could this issue you described happened on other test cases using Thread.suspend? e.g. BookKeeperClusterTestCase#sleepBookie. > TestSubAfterCloseSub fails strangely in tests > --------------------------------------------- > > Key: BOOKKEEPER-533 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-533 > Project: Bookkeeper > Issue Type: Bug > Reporter: Ivan Kelly > Assignee: Ivan Kelly > Fix For: 4.2.0 > > Attachments: BOOKKEEPER-513.diff, BOOKKEEPER-513.diff, > BOOKKEEPER-533.diff, BOOKKEEPER-533.diff, BOOKKEEPER-533.diff, > BOOKKEEPER-533.diff, BOOKKEEPER-533.diff, BOOKKEEPER-533.diff, > BOOKKEEPER-533.diff, BOOKKEEPER-533.diff, BOOKKEEPER-533.diff, > hedwig-server.log, stack.txt > > > Example https://builds.apache.org/job/bookkeeper-trunk-precommit-build/204/ > It looks like the maven surefire process exits, as if System.exit() is being > called. This should be the case since BOOKKEEPER-522, which removes all calls > to System.exit() -- 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