You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2007/04/15 19:40:16 UTC
[jira] Closed: (DERBY-2003) Use a lower wait timeout in
BlobClob4BlobTest
[ https://issues.apache.org/jira/browse/DERBY-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen closed DERBY-2003.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Assignee: Daniel John Debrunner
Fixed in revision 468209.
> Use a lower wait timeout in BlobClob4BlobTest
> ---------------------------------------------
>
> Key: DERBY-2003
> URL: https://issues.apache.org/jira/browse/DERBY-2003
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Knut Anders Hatlen
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.