Derby
  1. Derby
  2. DERBY-1455

Intermittent failure in derbynet/runtimeinfo.java

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.2.1.6
    • Fix Version/s: 10.2.1.6
    • Component/s: Test
    • Labels:
      None
    • Issue & fix info:
      Patch Available

      Description

      I often see failures of this type in derbynet/runtimeinfo.java:

                      • Diff file derbyall/derbynetclientmats/DerbyNetClient/derbynetmats/derbynetmats/runtimeinfo.diff
          • Start: runtimeinfo jdk1.5.0_04 DerbyNetClient derbynetmats:derbynetmats 2006-01-20 23:19:43 ***
            57a58,66
            > Session # :4
            > Database :wombat;create=true
            > User :APP
            > # Statements:2
            > Prepared Statement Information:
            > Stmt ID SQLText
            > ------------- -----------
            > SYSLH0002 VALUES(2)
            > SYSLH0001 SELECT count from sys.systables
            61 del
            < # Active Sessions : 1
            61a70
            > # Active Sessions : 2
            Test Failed.
          • End: runtimeinfo jdk1.5.0_04 DerbyNetClient derbynetmats:derbynetmats 2006-01-20 23:19:51 ***

      It doesn't seem to happen very frequently in Ole's nightly testing, but it has occurred there too:

      http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/testlog/SunOS-5.10_i86pc-i386/386483-derbyall_diff.txt
      http://www.multinet.no/~solberg/public/Apache/Derby/testlog/Linux-2.6.14-1.1644_FC4_i686-i686/354827-derbyall_diff.txt
      http://www.multinet.no/~solberg/public/Apache/Derby/testlog/Linux-2.6.14-1.1644_FC4_i686-i686/355169-derbynetmats_diff.txt
      http://www.multinet.no/~solberg/public/Apache/Derby/testlog/SunOS-5.10_i86pc-i386/321161-derbynetclientmats_diff.txt
      http://www.multinet.no/~solberg/public/Apache/Derby/testlog/SunOS-5.10_i86pc-i386/370878-derbyall_diff.txt

      1. derby-1455.diff
        0.8 kB
        Knut Anders Hatlen
      2. derby-1455.stat
        0.1 kB
        Knut Anders Hatlen

        Activity

        Gavin made changes -
        Workflow jira [ 12374355 ] Default workflow, editable Closed status [ 12799631 ]
        Knut Anders Hatlen made changes -
        Resolution Fixed [ 1 ]
        Status In Progress [ 3 ] Closed [ 6 ]
        Fix Version/s 10.2.0.0 [ 11187 ]
        Hide
        Knut Anders Hatlen added a comment -

        Committed revision 417131.

        Show
        Knut Anders Hatlen added a comment - Committed revision 417131.
        Knut Anders Hatlen made changes -
        Derby Info [Patch Available]
        Knut Anders Hatlen made changes -
        Attachment derby-1455.diff [ 12335870 ]
        Attachment derby-1455.stat [ 12335871 ]
        Hide
        Knut Anders Hatlen added a comment -

        Attached a patch which seems to fix the problem. I ran the test 421 times with the jar files from the 10.2.0.3 snapshot, and it failed 337 times (80% of the time). With the patch applied, I ran the test 814 times without any failures.

        The problem occurs when the test has opened four connections, closes three of them and runs getRuntimeInfo() on the server. The test expects that there is one active session on the server, but in some cases, the network server has not had enough time to clean up after the closed connections, and more sessions are listed as active.

        The patch solves this timing issue by invoking Thread.sleep(1000) before calling getRuntimeInfo().

        Show
        Knut Anders Hatlen added a comment - Attached a patch which seems to fix the problem. I ran the test 421 times with the jar files from the 10.2.0.3 snapshot, and it failed 337 times (80% of the time). With the patch applied, I ran the test 814 times without any failures. The problem occurs when the test has opened four connections, closes three of them and runs getRuntimeInfo() on the server. The test expects that there is one active session on the server, but in some cases, the network server has not had enough time to clean up after the closed connections, and more sessions are listed as active. The patch solves this timing issue by invoking Thread.sleep(1000) before calling getRuntimeInfo().
        Knut Anders Hatlen made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Knut Anders Hatlen created issue -

          People

          • Assignee:
            Knut Anders Hatlen
            Reporter:
            Knut Anders Hatlen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development