[DERBY-2003] Use a lower wait timeout in BlobClob4BlobTest

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: Test
• Assignee: Daniel John Debrunner
• Reporter: Knut Anders Hatlen
• Created: 26/Oct/06 06:52
• Updated: 15/Apr/07 17:39
• Resolved: 15/Apr/07 17:39

Description

These test cases wait 60 seconds for a timeout:

testLockingClob
testLockingWithLongRowClob
testLockingBlob
testLockingWithLongRowBlob

Since they run both in embedded and network client mode, BlobClob4BlobTest spends about eight minutes waiting for a timeout. Therefore, it would be good if its setUp() method lowered the timeout (and tearDown() reset it). TestJDBC40Exception shows how this could be achieved.

Issue Links

• is related to: DERBY-2004 jdbcapi/ConcurrencyTest sets system property in its suite() method