[ http://issues.apache.org/jira/browse/DERBY-2054?page=comments#action_12450774 ] Kristian Waagan commented on DERBY-2054: ----------------------------------------
Dan, could you please elaborate on the problems you see with the test? As far as I see, the only thing that would happen if super.tearDown is called, is that a rollback is issued and the the connection is closed. I do not understand how not doing this would affect other tests with regard of "the extra time needed to start the network server". I think that due to the other problems I had with converting the test, I forgot to close the connection manually. This would have to be done inside a try-block, where any exceptions are ignored. This is because setting the debug property causes havoc in the communication between the client and the server. My intention was that the network server I use is to be used only for this test, since simply unsetting the debug property is not enough for it to recover. Also, what authentication errors are you seeing? Thanks, > Rewrite 'derbynet/SuicideOfStreaming' to a JUnit test > ----------------------------------------------------- > > Key: DERBY-2054 > URL: http://issues.apache.org/jira/browse/DERBY-2054 > Project: Derby > Issue Type: Test > Components: Test > Affects Versions: 10.3.0.0 > Reporter: Kristian Waagan > Assigned To: Kristian Waagan > Priority: Minor > Fix For: 10.3.0.0 > > Attachments: derby-2054-1a.diff, derby-2054-1a.stat, > derby-2054-preview.diff > > > The test 'derbynet/SuicideOfStreaming' should be rewritten to a JUnit test > more in line with our newly created test system. > It is one of the last tests still being run from the deprecated > 'tests/junitTests/' directory, through a wrapper class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
