Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4709

Create test that parse client trace file to detect round-trips for Derby-4653

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 10.7.1.1
    • 10.7.1.1
    • Test
    • None
    • Newcomer

    Description

      In DERBY-4653, Kristian suggested we have a test that parse the trace file to detect round-trip Connection.flowcommit() instead of calling getClientTransactionID() method. The existing test for DERBY-4653 is in J2EEDataSourceTest.testConnectionFlowCommit(). When this issue get fixed, the call for getClientTransactionID can be replace with trace file parsing.

      Attachments

        1. derby-4709-1a-alternative_test.diff
          11 kB
          Kristian Waagan
        2. derby-4709-1b-alternative_test.diff
          11 kB
          Kristian Waagan
        3. derby-4709-1c-alternative_test.diff
          11 kB
          Kristian Waagan

        Issue Links

          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. DERBY-4717 Driver trace file isn't closed/released on physical connection close when specified with the traceFile attribute/setter

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is part of

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-4653 Avoid unnecessary round-trip for commit in the client driver

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              kristwaa Kristian Waagan
              lilywei Lily Wei
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: