Derby
  1. Derby
  2. 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

    Details

    • Type: Task Task
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 10.3.1.4
    • Fix Version/s: None
    • Component/s: Test
    • Urgency:
      Normal

      Description

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

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Myrna van Lunteren
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development