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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2009/03/04 23:57:58 UTC

[jira] Resolved: (DERBY-4036) Intermittent failure in jdbcapi/checkDataSource30.java with Derby 10.2 release

     [ https://issues.apache.org/jira/browse/DERBY-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren resolved DERBY-4036.
---------------------------------------

    Resolution: Won't Fix

marking won't fix. If someone feels inclined to fix this after all, this issue can be reopend.

> 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.