Derby
  1. Derby
  2. DERBY-4151

java.net.ConnectException in J2EEDataSourceTest (with network server) on IBM iseries

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.5.1.1, 10.5.3.1, 10.6.1.0
    • Component/s: Test
    • Labels:
      None
    • Environment:
      IBM iseries, OS: AS/400; OS version: V5R4M0, jvm: IBM 1.5 (build 1.5.0_13-b05) , IBM 1.6 (1.6.0_b105)
    • Bug behavior facts:
      Regression, Regression Test Failure

      Description

      12 of the fixtures of the J2EEDataSource test fail on iseries, with failures like this:

      23) testConnectionErrorEvent(org.apache.derbyTesting.functionTests.tests.jdbcapi.J2EEDataSourceTest)java.sql.SQLException: Error starting network server
      at java.lang.Throwable.<init>(Throwable.java:196)
      at java.lang.Exception.<init>(Exception.java:41)
      at java.sql.SQLException.<init>(SQLException.java:80)
      at org.apache.derbyTesting.junit.TestConfiguration.startNetworkServer(TestConfiguration.java:1455)
      at org.apache.derbyTesting.functionTests.tests.jdbcapi.J2EEDataSourceTest.testConnectionErrorEvent(J2EEDataSourceTest.java:615)
      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:84)
      at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
      at junit.extensions.TestSetup.run(TestSetup.java:23)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
      at junit.extensions.TestSetup.run(TestSetup.java:23)
      at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
      at junit.extensions.TestSetup.run(TestSetup.java:23)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      Caused by: java.lang.reflect.InvocationTargetException
      at java.lang.Exception.<init>(Exception.java:77)
      at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:54)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at org.apache.derbyTesting.junit.NetworkServerControlWrapper.invoke(NetworkServerControlWrapper.java:94)
      at org.apache.derbyTesting.junit.NetworkServerControlWrapper.ping(NetworkServerControlWrapper.java:106)
      at org.apache.derbyTesting.junit.TestConfiguration.startNetworkServer(TestConfiguration.java:1439)
      ... 38 more
      Caused by: java.lang.Exception: DRDA_NoIO.S:Could not connect to Derby Network Server on host 127.0.0.1, port 1527: A remote host refused an attempted connect operation.
      at java.lang.Throwable.<init>(Throwable.java:196)
      at java.lang.Exception.<init>(Exception.java:41)
      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)
      ... 44 more

      My classpath (in case it matters) contains:
      derbytools.jar:derbyclient.jar:derbynet.jar:derbyrun.jar:derbyTesting.jar:junit.jar

      1. derby.log
        6 kB
        Myrna van Lunteren
      2. error-stacktrace.out
        4 kB
        Myrna van Lunteren
      3. serverConsoleOutput.log
        2 kB
        Myrna van Lunteren
      4. DERBY-4151.diff
        0.9 kB
        Myrna van Lunteren

        Activity

        Hide
        Myrna van Lunteren added a comment -

        I'm trying to figure out what's up with these failures. I'm not done with my research, but thought I'd document what I found so far:
        The problem occurs with both ibm1.5 and ibm1.6 jvms.
        With 10.4. there were no such troubles - but with all 10.5 versions (and recent builds of trunk) there are.
        It's only the network server runs of the fixtures.
        I ran with 10.4.2.0 jars and a recent derbyTesting.jar and got failures; hence, it seems something in the test changed that made these failures appear.
        I looked at the test's changes, and did some further experiments with a recent 10.6 alpha build (830420) and derbyTesting.jar files from older builds close from around the time of the changes to the test, and found that after revision 675870 for DERBY-3319 11 tests fail.
        Revision 654870 added the following fixtures:
        testCloseActiveConnection_DS
        testCloseActiveConnection_CP
        testCloseActiveConnection_XA_local
        testCloseActiveConnection_XA_global
        It's interesting to note that the first test failure is the second test run after these "new" additions:
        ---------------------------------------------
        ...(fixtures pass until here...)
        testBadConnectionAttributeSyntax used 26 ms .
        testCloseActiveConnection_DS used 220 ms .
        testCloseActiveConnection_CP used 124 ms .
        testCloseActiveConnection_XA_local used 142 ms .
        testCloseActiveConnection_XA_global used 111 ms .
        testDescriptionProperty used 43 ms .
        testConnectionErrorEvent used 10698 ms E.
        testConnectionEventListenerIsNull used 15 ms E.
        testReadOnlyToWritableTran used 14 ms E.
        testAutoCommitOnXAResourceStart used 13 ms E.
        testAllDataSources used 13 ms E.
        testClosedCPDSConnection used 14 ms E.
        testClosedXADSConnection used 16 ms E.
        testSetSchemaInXAConnection used 13 ms E.
        testPooledReuseOnClose used 15 ms E.
        testSchemaIsReset used 13 ms E.
        testSchemaIsResetWhenDeleted used 12 ms E.
        testClientDSConnectionAttributes used 254 ms .
        ...(remaining fixtures pass)...
        ---------------------------------------------

        Show
        Myrna van Lunteren added a comment - I'm trying to figure out what's up with these failures. I'm not done with my research, but thought I'd document what I found so far: The problem occurs with both ibm1.5 and ibm1.6 jvms. With 10.4. there were no such troubles - but with all 10.5 versions (and recent builds of trunk) there are. It's only the network server runs of the fixtures. I ran with 10.4.2.0 jars and a recent derbyTesting.jar and got failures; hence, it seems something in the test changed that made these failures appear. I looked at the test's changes, and did some further experiments with a recent 10.6 alpha build (830420) and derbyTesting.jar files from older builds close from around the time of the changes to the test, and found that after revision 675870 for DERBY-3319 11 tests fail. Revision 654870 added the following fixtures: testCloseActiveConnection_DS testCloseActiveConnection_CP testCloseActiveConnection_XA_local testCloseActiveConnection_XA_global It's interesting to note that the first test failure is the second test run after these "new" additions: --------------------------------------------- ...(fixtures pass until here...) testBadConnectionAttributeSyntax used 26 ms . testCloseActiveConnection_DS used 220 ms . testCloseActiveConnection_CP used 124 ms . testCloseActiveConnection_XA_local used 142 ms . testCloseActiveConnection_XA_global used 111 ms . testDescriptionProperty used 43 ms . testConnectionErrorEvent used 10698 ms E. testConnectionEventListenerIsNull used 15 ms E. testReadOnlyToWritableTran used 14 ms E. testAutoCommitOnXAResourceStart used 13 ms E. testAllDataSources used 13 ms E. testClosedCPDSConnection used 14 ms E. testClosedXADSConnection used 16 ms E. testSetSchemaInXAConnection used 13 ms E. testPooledReuseOnClose used 15 ms E. testSchemaIsReset used 13 ms E. testSchemaIsResetWhenDeleted used 12 ms E. testClientDSConnectionAttributes used 254 ms . ...(remaining fixtures pass)... ---------------------------------------------
        Hide
        Myrna van Lunteren added a comment -

        I find that a suite of the following fixtures (in this sequence) will cause the failure in the testConnectionErrorEvent fixture:
        testGlobalLocalInterleaf
        testCloseActiveConnection_CP
        testCloseActiveConnection_XA_local
        testDescriptionProperty
        testConnectionErrorEvent
        Leaving any of these fixtures out will make the test pass.

        Show
        Myrna van Lunteren added a comment - I find that a suite of the following fixtures (in this sequence) will cause the failure in the testConnectionErrorEvent fixture: testGlobalLocalInterleaf testCloseActiveConnection_CP testCloseActiveConnection_XA_local testDescriptionProperty testConnectionErrorEvent Leaving any of these fixtures out will make the test pass.
        Hide
        Myrna van Lunteren added a comment -

        attaching files from the testfailure.

        Show
        Myrna van Lunteren added a comment - attaching files from the testfailure.
        Hide
        Myrna van Lunteren added a comment -

        I got one pass with only 4 tests, then the same set failed, which caused me to believe it was a matter of cleaning up.
        Adding some close() calls to 3 of the fixtures that were affected and the problem goes away.
        I'll commit later.

        Show
        Myrna van Lunteren added a comment - I got one pass with only 4 tests, then the same set failed, which caused me to believe it was a matter of cleaning up. Adding some close() calls to 3 of the fixtures that were affected and the problem goes away. I'll commit later.
        Hide
        Myrna van Lunteren added a comment -

        committed with revision 831584.
        I plan to backport this to 10.5 later.

        Show
        Myrna van Lunteren added a comment - committed with revision 831584. I plan to backport this to 10.5 later.
        Hide
        Myrna van Lunteren added a comment -

        backported to 10.5 with revision 831738.

        Show
        Myrna van Lunteren added a comment - backported to 10.5 with revision 831738.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development