[
https://issues.apache.org/jira/browse/DERBY-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668666#action_12668666
]
Myrna van Lunteren commented on DERBY-4036:
-------------------------------------------
I think this is either a test failure, or, maybe, a failure as a result of
DERBY-3172?
If a test failure, it got fixed by converting to junit (in 10.3) - if
DERBY-3172, it got fixed in 10.3...
I don't think it's worth our while for this rare intermittent failure to
backport possible changes to 10.2...
I suggest we close this as no fix intended, unless someone is of a different
opinion?
> Intermittent failure in jdbcapi/checkDataSource30.java with Derby 10.2 release
> ------------------------------------------------------------------------------
>
> Key: DERBY-4036
> URL: https://issues.apache.org/jira/browse/DERBY-4036
> Project: Derby
> Issue Type: Test
> Components: Regression Test Failure
> Affects Versions: 10.2.2.1
> Reporter: Mamta A. Satoor
> Priority: Minor
>
> On Derby 10.2, one can run into following intermittent failure with
> jdbcapi/checkDataSource30.java. In 10.2 release, this test is still written
> in old test harness rather than junit
> *** Start: checkDataSource30 jdk1.5.0 DerbyNetClient derbynetmats:jdk14
> 2009-01-29 03:59:43 ***
> 676a677
> > EVENT(6):connectionClosed
> Test Failed.
> *** End: checkDataSource30 jdk1.5.0 DerbyNetClient derbynetmats:jdk14
> 2009-01-29 04:00:13 ***
> We don't run into this in newer Derby releases because this test just been
> converted into junit test and as a junit test, the failure has not manifested
> itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
