[
https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615365#action_12615365
]
Kathey Marsden commented on DERBY-1764:
---------------------------------------
Hi Erlend,
I filed DERBY-3789 for the encrypted shutdown problem. It appears to be a bug
in Derby, but I also noticed this in the test. We have the method:
private void select(String table) throws SQLException {
Statement s = con.createStatement();
try {
s.executeQuery("select * from " + table);
} catch (SQLException se) {
String e = se.getSQLState();
if (e.equals("42Y55") || e.equals("42000") || e.equals("40001")
|| e.equals("40XL1") || e.equals("40XL2")
|| e.equals("42Y07")) {
// ignore these
} else {
throw se;
}
}finally {
s = null;
}
}
Which doesn't actually select all the results. It should do a next through the
table and then close the ResultSet. Perhaps that will help us avoid
DERBY-3789 as well.
> Rewrite stress.multi as a JUnit test
> ------------------------------------
>
> Key: DERBY-1764
> URL: https://issues.apache.org/jira/browse/DERBY-1764
> Project: Derby
> Issue Type: Test
> Components: Test
> Reporter: Knut Anders Hatlen
> Assignee: Erlend Birkenes
> Attachments: derby-1764-3a-whitespace_changes.diff,
> derby-1764-derby.log, DERBY-1764-Review.diff, DERBY-1764-V1.diff,
> DERBY-1764-V2.diff, DERBY-1764_4.diff
>
>
> Currently, stress.multi consists of a number of sql scripts that are run in
> ij. It often fails with cryptic error messages, and since it uses ij, there
> is often no stack trace. It would be very useful to rewrite the test in JUnit
> so that we can get better error messages and stack traces when it fails.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
