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 "Shreyas Kaushik (JIRA)" <de...@db.apache.org> on 2005/05/02 06:01:05 UTC
[jira] Closed: (DERBY-226) intermittent SQLException in test jdbcapi/testRelative.java
[ http://issues.apache.org/jira/browse/DERBY-226?page=all ]
Shreyas Kaushik closed DERBY-226:
---------------------------------
Assign To: Shreyas Kaushik
Resolution: Fixed
Closing this as this has been fixed.
> intermittent SQLException in test jdbcapi/testRelative.java
> -----------------------------------------------------------
>
> Key: DERBY-226
> URL: http://issues.apache.org/jira/browse/DERBY-226
> Project: Derby
> Type: Bug
> Versions: 10.0.2.1
> Reporter: Myrna van Lunteren
> Assignee: Shreyas Kaushik
> Fix For: 10.0.2.2
>
> There is an intermittent failure in the test jdbcapi/testRelative.java.
> The diff is similar to the following:
> 6a7
> > SQL Exception: Invalid cursor state - no current row.
> 9 del
> < SQL Exception: Invalid cursor state - no current row.
> Test Failed.
> It might be a timing issue related to doing a sqle.printStackTrace() in the case of an expected exception.
> The issue maybe with more than the test - but the test also has a problem:
> the master shows that we have an unexpected exception which doesn't make
> sense in the master.
> Generally only expected exceptions would be checked into the master and
> would not print a stack trace.
> Unexpected exceptions should cause the test to fail and should print a
> stack trace.
> Further analysis is necessary to identify why there is an exception & why it /its timing is intermittent.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira