[
https://issues.apache.org/jira/browse/DERBY-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088776#comment-13088776
]
Siddharth Srivastava commented on DERBY-5382:
---------------------------------------------
Hi
Just wanted to share some observation while writing this test (which went
automagically)
I receoved the following errors:
1) A lock could not be obtained within the time requested
I see that it was resolved in Derby-4273. But the consistently nagged me
throughout the day. As a hack I used Thread.interrupted() while committing
changes.
Problem ceased to exist after this, but later when I rebuilt the same code
without Thread.interrupted(), all went fine.
2) SQLNonTransientConnectionException: No current connection.. again after
dealing with it for hours (tried System.gc() and everything else), it also went
automagically.
If I remember correctly, there was a Jira issue related to this, but it also
mentioned somewhere that this error is not reproducible frequently.
3) This test initially failed when I used
String tableName = "RecTest", but when I used String tableName = "RECTEST1",
the error again went away.
I guess it is something like the discussion in Derby-437.
May be a reference in the doc(may be a footer explaining non delimited and
delimited identifiers), would be good.
Can anyone familiar with these errors, help me in understanding them better(or
reproducing them), so that I can get some insight that it was due to some
system issues(I have been facing strange file permission issues within my local
derby repo) or some fault in the patch.
Thanks
> Convert existing harness recovery tests to JUnit tests
> ------------------------------------------------------
>
> Key: DERBY-5382
> URL: https://issues.apache.org/jira/browse/DERBY-5382
> Project: Derby
> Issue Type: Improvement
> Reporter: Siddharth Srivastava
> Assignee: Siddharth Srivastava
> Attachments: d5382.patch
>
>
> Existing harness recovery tests need to be converted to JUnit tests. A
> framework as designed in Derby-4249 can be used for this purpose.
> Tests to be converted:
> a) oc_rec1
> b) oc_rec2
> c) oc_rec3
> d) oc_rec4
> These recovery tests run in coordination. The test oc_rec1 creates a table,
> inserts and then deletes rows from it and commit it which is followed by a
> series of insertion of rows in the existing table in oc_rec2, oc_rec3 and
> oc_rec4. The tests oc_rec2 and oc_3 also create table and insert, delete,
> compress rows in it and leave the table thus produced in committed or
> uncommitted state which is tested by the next corresponding test (oc_rec3 for
> oc_rec2, oc_rec4 for oc_rec3) for recovery.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
