[
https://issues.apache.org/jira/browse/DERBY-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2533:
----------------------------------
Component/s: Test
marking as test component to track analysis proposed. After that if a bug is
found component should be changed to appropriate area.
> 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.0.0
> Reporter: Myrna van Lunteren
>
> 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.
-
You can reply to this email to add a comment to the issue online.
