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

ReplicationRun_Local.testReplication_Local_LogFilesSynched failed with connection refused

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.8.1.2, 10.8.2.2
    • Fix Version/s: None
    • Component/s: Replication, Test
    • Urgency:
      Normal
    • Bug behavior facts:
      Regression Test Failure

      Description

      Seen when testing 10.8.1.1 on SUSE:

      http://dbtg.foundry.sun.com/derby/test/10.8.1.1_RC/logs/jvm1.6-64/sles/suitesAll/report.txt

      There was 1 error:
      1) testReplication_Local_LogFilesSynched(org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local)java.lang.Exception: DRDA_NoIO.S:Could not connect to Derby Network Server on host 127.0.0.1, port 1527: Connection refused
      at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(Unknown Source)
      at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(Unknown Source)
      at org.apache.derby.impl.drda.NetworkServerControlImpl.setUpSocket(Unknown Source)
      at org.apache.derby.impl.drda.NetworkServerControlImpl.ping(Unknown Source)
      at org.apache.derby.drda.NetworkServerControl.ping(Unknown Source)
      at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.ping(ReplicationRun.java:2632)
      at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.pingServer(ReplicationRun.java:2619)
      at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.startServer(ReplicationRun.java:2291)
      at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local.testReplication_Local_LogFilesSynched(ReplicationRun_Local.java:180)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:112)
      at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.runBare(ReplicationRun.java:207)
      at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
      at junit.extensions.TestSetup.run(TestSetup.java:25)

        Activity

        Hide
        knutanders Knut Anders Hatlen added a comment -

        The fail directory didn't contain db_slave-derby.log or db_master-derby.log.

        Show
        knutanders Knut Anders Hatlen added a comment - The fail directory didn't contain db_slave-derby.log or db_master-derby.log.
        Hide
        knutanders Knut Anders Hatlen added a comment -

        Similar stack traces were seen in two other replication test cases when testing the 10.8.2.2 release candidate: http://dbtg.foundry.sun.com/derby/test/10.8.2.2_RC/logs/jvm1.6/sles/suitesAll/report.txt

        I'm not filing separate JIRA issues for each failing test case for now, on the assumption that they all have the same root cause.

        Show
        knutanders Knut Anders Hatlen added a comment - Similar stack traces were seen in two other replication test cases when testing the 10.8.2.2 release candidate: http://dbtg.foundry.sun.com/derby/test/10.8.2.2_RC/logs/jvm1.6/sles/suitesAll/report.txt I'm not filing separate JIRA issues for each failing test case for now, on the assumption that they all have the same root cause.

          People

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

            Dates

            • Created:
              Updated:

              Development