[DERBY-5014] Tests should restore the timeout values to default after they are done running.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.7.1.1
• Fix Version/s: 10.8.2.2, 10.9.1.0
• Component/s: Test
• Labels: derby_backport_reject_10_5
• Urgency: Normal
• Issue & fix info: Known fix, Newcomer
• Assignee: Siddharth Srivastava
• Reporter: Mamta A. Satoor
• Created: 08/Feb/11 22:57
• Updated: 15/Nov/13 08:15
• Resolved: 12/Sep/12 23:20

Description

There are still couple more tests that change the lock time out during the test run but don't restore it to the default at the
end of the test. Knut already fixed this behavior for SetTransactionIsolationTest.java and ResultSetMiscTest.java as part of DERBY-4273
Following are some additional tests that should be fixed
1)ErrorMessageTest.java 2)StressMultiTest.java 3)Sttest.java 4)SysinfoTest.java 5)DatabaseMetaDataTest.java 6)ResultSetsFromPreparedStatementTest.java