db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-2533) Analysis needed on local/global interleaf of global/local connections to see if locks remaining open is acceptable, and why it gives Protocol errors with DerbyNetClient on subsequent connections to db
Date Tue, 13 Aug 2013 22:38:48 GMT

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

Myrna van Lunteren updated DERBY-2533:
--------------------------------------

    Urgency: Normal
     Labels: derby_triage10_11  (was: )
    
> Analysis needed on local/global interleaf of global/local connections to see if locks
remaining open is acceptable, and why it gives Protocol errors with DerbyNetClient on subsequent
connections to db
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2533
>                 URL: https://issues.apache.org/jira/browse/DERBY-2533
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.1.4
>            Reporter: Myrna van Lunteren
>              Labels: derby_triage10_11
>
> This reflects the state that the database is left at in test DataSourceTest.java, converted
to junit from the original checkDataSource.java and checkDataSource30.java.
> The original test also left the database in a bad state, but because each test would
run in a separate jvm and db, this only showed up during remote server testing.
> The current test DataSourceTest.java shows the bad state in fixtures testGlobaLocalInterleaf()
and testReuseAcrossGlobalLocal() if one does not shutdown the database with Embedded, or if
one runs the test with Client (by commenting out the if (usingDerbyNetClient() return; lines).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message