Derby
  1. Derby
  2. DERBY-4180

SQLTransactionRollbackException in XATransactionTest when testing client/server compatibility

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 10.5.1.1
    • Fix Version/s: None
    • Component/s: Test
    • Labels:
      None
    • Environment:
      Windows Vista 64, AMD Phenom II 940, Sun JDK 1.6.0_10, JUnit 3.8.2
    • Bug behavior facts:
      Regression, Regression Test Failure

      Description

      When running suites.All on a 10.4 client to 10.5 server configuration, the failure was observed.

      10.5 Jars - From the db-derby-10.5.1.1-bin.zip (RC2 - sane)
      ==============================================
      derby.jar
      derbytools.jar
      derbyLocale*.jar
      derbyrun.jar
      derbynet.jar

      10.4 jars - (Built from the 10.4 branch - sane)
      ===================================
      derbyTesting.jar
      derbyClient.jar

      Stack Trace
      =========
      5) testXATransactionTimeout(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest)java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested
      at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
      at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
      at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest.testXATransactionTimeout(XATransactionTest.java:234)
      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:102)
      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)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      Caused by: java.sql.SQLException: A lock could not be obtained within the time requested
      at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)
      ... 39 more
      Caused by: ERROR 40XL1: A lock could not be obtained within the time requested
      at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
      at org.apache.derby.impl.services.locks.ConcurrentLockSet.lockObject(Unknown Source)
      at org.apache.derby.impl.services.locks.ConcurrentLockSet.zeroDurationLockObject(Unknown Source)
      at org.apache.derby.impl.services.locks.AbstractPool.zeroDurationlockObject(Unknown Source)
      at org.apache.derby.impl.services.locks.ConcurrentPool.zeroDurationlockObject(Unknown Source)
      at org.apache.derby.impl.store.raw.xact.RowLocking2nohold.lockRecordForRead(Unknown Source)
      at org.apache.derby.impl.store.access.conglomerate.OpenConglomerate.lockPositionForRead(Unknown Source)
      at org.apache.derby.impl.store.access.conglomerate.GenericScanController.fetchRows(Unknown Source)
      at org.apache.derby.impl.store.access.heap.HeapScan.fetchNextGroup(Unknown Source)
      at org.apache.derby.impl.sql.execute.BulkTableScanResultSet.reloadArray(Unknown Source)
      at org.apache.derby.impl.sql.execute.BulkTableScanResultSet.getNextRowCore(Unknown Source)
      at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.getNextRowCore(Unknown Source)
      at org.apache.derby.impl.sql.execute.ScalarAggregateResultSet.getRowFromResultSet(Unknown Source)
      at org.apache.derby.impl.sql.execute.ScalarAggregateResultSet.getNextRowCore(Unknown Source)
      at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.getNextRowCore(Unknown Source)
      at org.apache.derby.impl.sql.execute.BasicNoPutResultSetImpl.getNextRow(Unknown Source)
      ... 32 more

      1. javacore.20090611.094630.6388.0001.txt
        1.37 MB
        Mamta A. Satoor
      2. hangInfo061109.txt
        17 kB
        Mamta A. Satoor

        Issue Links

          Activity

          Hide
          Mamta A. Satoor added a comment -

          I downloaded the jar files for 10.5.1.1 and 10.4.2 release. I used following to setup the environment before running the junit test
          cd \mydocs\realdocs\bugs\Derby4180*
          sh
          export CLASSPATH="C:\p4clients\main\tools\java\junit.jar;derby10.5.1.1\derbynet.jar;derby10.5.1.1\derbytools.jar;derby10.4.2\derbyclient.jar;derby10.4.2\derbyTesting.jar;c:\p4clients\main\ibm16\lib;$CLASSPATH"
          export PATH="c:\p4clients\main\ibm16\bin;$PATH"

          As indicated by the classpath above, the server jar files come from 10.5.1.1 (ie derbynet.jar and derbytools.jar)

          The client jar files come from 10.4.2 (ie derbyclient.jar and derbyTesting.jar)

          With the environment above, when I run the problem junit test XATransactionTest, I do not see any failures.
          java -Xmx1024m junit.swingui.TestRunner -noloading
          org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest

          I downloaded the jar files from http://db.apache.org/derby/releases/release-10.4.2.0.cgi and http://db.apache.org/derby/releases/release-10.5.1.1.cgi

          Is this an intermittent failure and I need to run it multiple times to run into it? Or is there anything wrong with my setup?

          I did notice that the jira says the problem was found when the entire junit suite was run. I will fire suites.All to see if the problem manifests itself.

          Show
          Mamta A. Satoor added a comment - I downloaded the jar files for 10.5.1.1 and 10.4.2 release. I used following to setup the environment before running the junit test cd \mydocs\realdocs\bugs\Derby4180* sh export CLASSPATH="C:\p4clients\main\tools\java\junit.jar;derby10.5.1.1\derbynet.jar;derby10.5.1.1\derbytools.jar;derby10.4.2\derbyclient.jar;derby10.4.2\derbyTesting.jar;c:\p4clients\main\ibm16\lib;$CLASSPATH" export PATH="c:\p4clients\main\ibm16\bin;$PATH" As indicated by the classpath above, the server jar files come from 10.5.1.1 (ie derbynet.jar and derbytools.jar) The client jar files come from 10.4.2 (ie derbyclient.jar and derbyTesting.jar) With the environment above, when I run the problem junit test XATransactionTest, I do not see any failures. java -Xmx1024m junit.swingui.TestRunner -noloading org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest I downloaded the jar files from http://db.apache.org/derby/releases/release-10.4.2.0.cgi and http://db.apache.org/derby/releases/release-10.5.1.1.cgi Is this an intermittent failure and I need to run it multiple times to run into it? Or is there anything wrong with my setup? I did notice that the jira says the problem was found when the entire junit suite was run. I will fire suites.All to see if the problem manifests itself.
          Hide
          Mamta A. Satoor added a comment -

          I talked to Kathey about this jira entry and she mentioned that the behavior was noticed with the client as the 10.4 latest codeline( I was trying to use the jar files for 10.4.2 release). Also, she mentioned that the test XA40Test hangs when the junit suite is run so it will be better to comment out that test and then run the junit suite.

          I have updated my 10.4 codeline with the latest changes and build the jar files after commenting XA40Test. I am using derbyTesting.jar and derbyclient.jar from the 10.4 codeline and I am continuing to use the 10.5 jars(for the server side) from http://db.apache.org/derby/releases/release-10.5.1.1.cgi

          With that configuration, when I run the junit suite using the gui interface as shown below, I run into out of memory errors
          java -Xmx1024m junit.swingui.TestRunner -noloading org.apache.derbyTesting.functionTests.suites.All

          I tried the text interface as show below but it seems to be hanging somewhere. The problem with text interface is there is no clue which test might be hanging.
          java -Xmx256M -XX:MaxPermSize=128M junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All

          I will go ahead and kill that text run and try to run the junit suite again with the text interface to see if I can reproduce the problem. I am using ibm16 on Windows XP box.

          Show
          Mamta A. Satoor added a comment - I talked to Kathey about this jira entry and she mentioned that the behavior was noticed with the client as the 10.4 latest codeline( I was trying to use the jar files for 10.4.2 release). Also, she mentioned that the test XA40Test hangs when the junit suite is run so it will be better to comment out that test and then run the junit suite. I have updated my 10.4 codeline with the latest changes and build the jar files after commenting XA40Test. I am using derbyTesting.jar and derbyclient.jar from the 10.4 codeline and I am continuing to use the 10.5 jars(for the server side) from http://db.apache.org/derby/releases/release-10.5.1.1.cgi With that configuration, when I run the junit suite using the gui interface as shown below, I run into out of memory errors java -Xmx1024m junit.swingui.TestRunner -noloading org.apache.derbyTesting.functionTests.suites.All I tried the text interface as show below but it seems to be hanging somewhere. The problem with text interface is there is no clue which test might be hanging. java -Xmx256M -XX:MaxPermSize=128M junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All I will go ahead and kill that text run and try to run the junit suite again with the text interface to see if I can reproduce the problem. I am using ibm16 on Windows XP box.
          Hide
          Mamta A. Satoor added a comment -

          Also, to simplify things, I have moved all the required jar files from 10.5 release and the one built by me for 10.4 client into one directory and the classpath now looks as follows
          export CLASSPATH="C:\p4clients\main\tools\java\junit.jar;derby.jar;derbynet.jar;derbytools.jar;derbyclient.jar;derbyTesting.jar;c:\p4clients\main\ibm16\lib;$CLASSPATH"

          I am running the tests right now with the text interface to see if the problem will reproduce.

          Show
          Mamta A. Satoor added a comment - Also, to simplify things, I have moved all the required jar files from 10.5 release and the one built by me for 10.4 client into one directory and the classpath now looks as follows export CLASSPATH="C:\p4clients\main\tools\java\junit.jar;derby.jar;derbynet.jar;derbytools.jar;derbyclient.jar;derbyTesting.jar;c:\p4clients\main\ibm16\lib;$CLASSPATH" I am running the tests right now with the text interface to see if the problem will reproduce.
          Hide
          Mamta A. Satoor added a comment -

          I am still not able to reproduce the problem. In fact, the juni test suite seems to be hanging somewhere. Since the text interface does not show what test it is running right now, I am not sure how to tell where the hang is.

          I am copying my environment setting and the test results until the hang as an attachment to this jira entry (attachment name hangInfo061109.txt). If anyone sees any problem with my setup or if I need to try something different to repro the problem, please let me know. I am pretty certain that I have commented XA40Test but I will check that again.

          Show
          Mamta A. Satoor added a comment - I am still not able to reproduce the problem. In fact, the juni test suite seems to be hanging somewhere. Since the text interface does not show what test it is running right now, I am not sure how to tell where the hang is. I am copying my environment setting and the test results until the hang as an attachment to this jira entry (attachment name hangInfo061109.txt). If anyone sees any problem with my setup or if I need to try something different to repro the problem, please let me know. I am pretty certain that I have commented XA40Test but I will check that again.
          Hide
          Kathey Marsden added a comment -

          Hi Mamta.

          You can run with -Dderby.tests.trace=true to see what test is running. Can you look at system/derby.log and see if you see a bind exception DERBY-4053. Also hit <ctrl> <break> when it is hung to get a javacore. Lastly try to do a NetworkServerControl ping and see if it hangs which would be another indicator of DERBY-4053

          If it is DERBY-4053, you might want to try running with the Sun JVM since it seems less likely to occur with that jvm.

          Show
          Kathey Marsden added a comment - Hi Mamta. You can run with -Dderby.tests.trace=true to see what test is running. Can you look at system/derby.log and see if you see a bind exception DERBY-4053 . Also hit <ctrl> <break> when it is hung to get a javacore. Lastly try to do a NetworkServerControl ping and see if it hangs which would be another indicator of DERBY-4053 If it is DERBY-4053 , you might want to try running with the Sun JVM since it seems less likely to occur with that jvm.
          Hide
          Mamta A. Satoor added a comment -

          Thank you, Kathey. I did Ctrl Break and got a long dump in a file. I am attaching it to jira as javacore.20090611.094630.6388.0001.txt

          Show
          Mamta A. Satoor added a comment - Thank you, Kathey. I did Ctrl Break and got a long dump in a file. I am attaching it to jira as javacore.20090611.094630.6388.0001.txt
          Hide
          Mamta A. Satoor added a comment -

          Yes, I did see the BindException. I will go ahead and run the tests with Sun's jdk and with -Dderby.tests.trace=true to see if I can repro the problem.

          Show
          Mamta A. Satoor added a comment - Yes, I did see the BindException. I will go ahead and run the tests with Sun's jdk and with -Dderby.tests.trace=true to see if I can repro the problem.
          Hide
          Mamta A. Satoor added a comment -

          the run with Sun's jdk16 also resulted into a hang and it seems like it might be the same test that hanged with ibm16. Following is the output right before and including the hanging test
          testCreateBlob used 47 ms .
          testConnectionIsValid used 125 ms java.lang.Exception: DRDA_InvalidReplyTooShort
          .S:Invalid reply from network server: Insufficient data.
          at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMe
          ssageWork(NetworkServerControlImpl.java:3179)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMe
          ssage(NetworkServerControlImpl.java:1835)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.fillReplyBuffer(N
          etworkServerControlImpl.java:2771)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(Networ
          kServerControlImpl.java:2708)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.pingWithNoOpen(Ne
          tworkServerControlImpl.java:1169)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.ping(NetworkServe
          rControlImpl.java:1144)
          at org.apache.derby.drda.NetworkServerControl.ping(NetworkServerControl.
          java:395)
          at org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerUp(
          NetworkServerTestSetup.java:546)
          at org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerSta
          rt(NetworkServerTestSetup.java:615)
          at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkSer
          verTestSetup.java:191)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          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.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:23)
          at junit.framework.TestSuite.runTest(TestSuite.java:208)
          at junit.framework.TestSuite.run(TestSuite.java:203)
          at junit.framework.TestSuite.runTest(TestSuite.java:208)
          at junit.framework.TestSuite.run(TestSuite.java:203)
          at junit.framework.TestSuite.runTest(TestSuite.java:208)
          at junit.framework.TestSuite.run(TestSuite.java:203)
          at junit.framework.TestSuite.runTest(TestSuite.java:208)
          at junit.framework.TestSuite.run(TestSuite.java:203)
          at junit.textui.TestRunner.doRun(TestRunner.java:116)
          at junit.textui.TestRunner.start(TestRunner.java:172)
          at junit.textui.TestRunner.main(TestRunner.java:138)
          F.
          testAllJDBCObjects used 438 ms

          I will comment out testAllJDBCObjects and see if the junit suite makes more progress and can repro the problem associated with this jira entry. BTW, is this hang with testAllJDBCObjects a known issue?

          Show
          Mamta A. Satoor added a comment - the run with Sun's jdk16 also resulted into a hang and it seems like it might be the same test that hanged with ibm16. Following is the output right before and including the hanging test testCreateBlob used 47 ms . testConnectionIsValid used 125 ms java.lang.Exception: DRDA_InvalidReplyTooShort .S:Invalid reply from network server: Insufficient data. at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMe ssageWork(NetworkServerControlImpl.java:3179) at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMe ssage(NetworkServerControlImpl.java:1835) at org.apache.derby.impl.drda.NetworkServerControlImpl.fillReplyBuffer(N etworkServerControlImpl.java:2771) at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(Networ kServerControlImpl.java:2708) at org.apache.derby.impl.drda.NetworkServerControlImpl.pingWithNoOpen(Ne tworkServerControlImpl.java:1169) at org.apache.derby.impl.drda.NetworkServerControlImpl.ping(NetworkServe rControlImpl.java:1144) at org.apache.derby.drda.NetworkServerControl.ping(NetworkServerControl. java:395) at org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerUp( NetworkServerTestSetup.java:546) at org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerSta rt(NetworkServerTestSetup.java:615) at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkSer verTestSetup.java:191) at junit.extensions.TestSetup$1.protect(TestSetup.java:18) at junit.framework.TestResult.runProtected(TestResult.java:124) 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.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:23) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.textui.TestRunner.doRun(TestRunner.java:116) at junit.textui.TestRunner.start(TestRunner.java:172) at junit.textui.TestRunner.main(TestRunner.java:138) F. testAllJDBCObjects used 438 ms I will comment out testAllJDBCObjects and see if the junit suite makes more progress and can repro the problem associated with this jira entry. BTW, is this hang with testAllJDBCObjects a known issue?
          Hide
          Kathey Marsden added a comment -

          It looks like those fixtures are in jdbc4.ConnectionMethodsTest
          Does that test hang on its own?
          If so, the only things that I can suggest are a) Try to fix DERBY-4053 first, which would be great because it seem to be becoming a real problem and it looks like you have a reproduction for it.
          or
          b) Comment out ConnectionMethodsTest and see if you can continue the test run and pop this issue.

          Show
          Kathey Marsden added a comment - It looks like those fixtures are in jdbc4.ConnectionMethodsTest Does that test hang on its own? If so, the only things that I can suggest are a) Try to fix DERBY-4053 first, which would be great because it seem to be becoming a real problem and it looks like you have a reproduction for it. or b) Comment out ConnectionMethodsTest and see if you can continue the test run and pop this issue.
          Hide
          Mamta A. Satoor added a comment -

          May be I reading it wrong but I thought testAllJDBCObjects fixture is in jdbc4.VerifySignatures and based on that, I commented out VerifySignatures from jdbc4._Suite.java

          Is that right or am I not reading the test run output correctly?

          BTW, I thought last night I commented out VerifySignatures and rebuilt the jars based on that and fired the junit tests using the new jars. But it seems like this morning, the tests were again hung at the same place. Maybe I missed one of the steps of rebuilding classes/jars/copying jars, not sure what. I have started the tests again this morning making sure I have taken care of all those steps and will see how the run goes.

          Show
          Mamta A. Satoor added a comment - May be I reading it wrong but I thought testAllJDBCObjects fixture is in jdbc4.VerifySignatures and based on that, I commented out VerifySignatures from jdbc4._Suite.java Is that right or am I not reading the test run output correctly? BTW, I thought last night I commented out VerifySignatures and rebuilt the jars based on that and fired the junit tests using the new jars. But it seems like this morning, the tests were again hung at the same place. Maybe I missed one of the steps of rebuilding classes/jars/copying jars, not sure what. I have started the tests again this morning making sure I have taken care of all those steps and will see how the run goes.
          Hide
          Mamta A. Satoor added a comment -

          I will run jdbc4.VerifySignatures on it's own to see if I can repro the hang.

          Show
          Mamta A. Satoor added a comment - I will run jdbc4.VerifySignatures on it's own to see if I can repro the hang.
          Hide
          Kathey Marsden added a comment -

          Sorry, I just noticed testAllJDBCObjects at the bottom. I think the real problem comes with
          testConnectionIsValid used 125 ms java.lang.Exception: DRDA_InvalidReplyTooShort
          .S:Invalid reply from network server: Insufficient data and then testAllJDBCObjects cannot start the server.

          So probably if you wanted to reproduce the circumstances you would need to run a small suite with both ConnectionMethodsTest and VerifySignatures.

          Unfortunately DERBY-4053 can really affect any network server test I think it is not usually the test that hangs, but rather the next one that tries to bring up and ping the server.

          Show
          Kathey Marsden added a comment - Sorry, I just noticed testAllJDBCObjects at the bottom. I think the real problem comes with testConnectionIsValid used 125 ms java.lang.Exception: DRDA_InvalidReplyTooShort .S:Invalid reply from network server: Insufficient data and then testAllJDBCObjects cannot start the server. So probably if you wanted to reproduce the circumstances you would need to run a small suite with both ConnectionMethodsTest and VerifySignatures. Unfortunately DERBY-4053 can really affect any network server test I think it is not usually the test that hangs, but rather the next one that tries to bring up and ping the server.
          Hide
          Mamta A. Satoor added a comment -

          This time around, I got the hang in a different test
          testCreateClob used 47 ms .
          testCreateBlob used 47 ms .
          testConnectionIsValid used 203 ms java.lang.Exception: DRDA_InvalidReplyTooShort
          .S:Invalid reply from network server: Insufficient data.
          at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMe
          ssageWork(NetworkServerControlImpl.java:3179)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMe
          ssage(NetworkServerControlImpl.java:1835)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.fillReplyBuffer(N
          etworkServerControlImpl.java:2771)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(Networ
          kServerControlImpl.java:2708)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.pingWithNoOpen(Ne
          tworkServerControlImpl.java:1169)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.ping(NetworkServe
          rControlImpl.java:1144)
          at org.apache.derby.drda.NetworkServerControl.ping(NetworkServerControl.
          java:395)
          at org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerUp(
          NetworkServerTestSetup.java:546)
          at org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerSta
          rt(NetworkServerTestSetup.java:615)
          at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkSer
          verTestSetup.java:191)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          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.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:23)
          at junit.framework.TestSuite.runTest(TestSuite.java:208)
          at junit.framework.TestSuite.run(TestSuite.java:203)
          at junit.framework.TestSuite.runTest(TestSuite.java:208)
          at junit.framework.TestSuite.run(TestSuite.java:203)
          at junit.framework.TestSuite.runTest(TestSuite.java:208)
          at junit.framework.TestSuite.run(TestSuite.java:203)
          at junit.framework.TestSuite.runTest(TestSuite.java:208)
          at junit.framework.TestSuite.run(TestSuite.java:203)
          at junit.textui.TestRunner.doRun(TestRunner.java:116)
          at junit.textui.TestRunner.start(TestRunner.java:172)
          at junit.textui.TestRunner.main(TestRunner.java:138)
          F.
          testReadWriteNoParameters used 94 ms .
          testReadNoParameterWriteOneParameter used 46 ms .
          testReadWriteOneParameter used 16 ms .
          testReadWriteThreeParameter used 0 ms .
          testEndOfStreamValue used 109 ms .
          testEndOfStreamOnReadOneParameter used 47 ms .
          testEndOfStreamOnReadThreeParameters used 47 ms .
          testSkip used 63 ms .
          testWriteWithInvalidParameterValues used 47 ms .
          testReadWithInvalidParameterValues used 62 ms .
          testReadWriteNoParameters used 156 ms .
          testReadNoParameterWriteOneParameter used 94 ms .
          testReadWriteOneParameter used 16 ms .

          testReadWriteThreeParameter used 15 ms .
          testEndOfStreamValue used 157 ms .
          testEndOfStreamOnReadOneParameter used 62 ms .
          testEndOfStreamOnReadThreeParameters used 63 ms .
          testSkip used 93 ms .
          testWriteWithInvalidParameterValues used 78 ms .
          testReadWithInvalidParameterValues used 63 ms .
          testSetBytesLargeBlob used 62 ms .
          testSetBytesSmallBlob used 78 ms

          Kathey, like you mentioned, DERBY-4053 is definitely more recurring that intermittent, atleast on my machine. I have run the tests 3 times so far and everytime the run has gotten hung

          Show
          Mamta A. Satoor added a comment - This time around, I got the hang in a different test testCreateClob used 47 ms . testCreateBlob used 47 ms . testConnectionIsValid used 203 ms java.lang.Exception: DRDA_InvalidReplyTooShort .S:Invalid reply from network server: Insufficient data. at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMe ssageWork(NetworkServerControlImpl.java:3179) at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMe ssage(NetworkServerControlImpl.java:1835) at org.apache.derby.impl.drda.NetworkServerControlImpl.fillReplyBuffer(N etworkServerControlImpl.java:2771) at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(Networ kServerControlImpl.java:2708) at org.apache.derby.impl.drda.NetworkServerControlImpl.pingWithNoOpen(Ne tworkServerControlImpl.java:1169) at org.apache.derby.impl.drda.NetworkServerControlImpl.ping(NetworkServe rControlImpl.java:1144) at org.apache.derby.drda.NetworkServerControl.ping(NetworkServerControl. java:395) at org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerUp( NetworkServerTestSetup.java:546) at org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerSta rt(NetworkServerTestSetup.java:615) at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkSer verTestSetup.java:191) at junit.extensions.TestSetup$1.protect(TestSetup.java:18) at junit.framework.TestResult.runProtected(TestResult.java:124) 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.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:23) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.textui.TestRunner.doRun(TestRunner.java:116) at junit.textui.TestRunner.start(TestRunner.java:172) at junit.textui.TestRunner.main(TestRunner.java:138) F. testReadWriteNoParameters used 94 ms . testReadNoParameterWriteOneParameter used 46 ms . testReadWriteOneParameter used 16 ms . testReadWriteThreeParameter used 0 ms . testEndOfStreamValue used 109 ms . testEndOfStreamOnReadOneParameter used 47 ms . testEndOfStreamOnReadThreeParameters used 47 ms . testSkip used 63 ms . testWriteWithInvalidParameterValues used 47 ms . testReadWithInvalidParameterValues used 62 ms . testReadWriteNoParameters used 156 ms . testReadNoParameterWriteOneParameter used 94 ms . testReadWriteOneParameter used 16 ms . testReadWriteThreeParameter used 15 ms . testEndOfStreamValue used 157 ms . testEndOfStreamOnReadOneParameter used 62 ms . testEndOfStreamOnReadThreeParameters used 63 ms . testSkip used 93 ms . testWriteWithInvalidParameterValues used 78 ms . testReadWithInvalidParameterValues used 63 ms . testSetBytesLargeBlob used 62 ms . testSetBytesSmallBlob used 78 ms Kathey, like you mentioned, DERBY-4053 is definitely more recurring that intermittent, atleast on my machine. I have run the tests 3 times so far and everytime the run has gotten hung
          Hide
          Kathey Marsden added a comment -

          I think now that DERBY-4053 is fixed we should be able to get through these tests without hanging. From the description of the original problem, it sounds like it too may be related to DERBY-4053. I will kick of a mixed version client/server run and verify.

          Show
          Kathey Marsden added a comment - I think now that DERBY-4053 is fixed we should be able to get through these tests without hanging. From the description of the original problem, it sounds like it too may be related to DERBY-4053 . I will kick of a mixed version client/server run and verify.
          Hide
          Kathey Marsden added a comment -

          Running on the latest on the 10.5 and 10.4 branches:
          [/home/kmarsden/testjars/derby.jar] 10.5.2.1 - (800568)
          [/home/kmarsden/testjars/derbytools.jar] 10.5.2.1 - (800568)
          [/home/kmarsden/testjars/derbynet.jar] 10.5.2.1 - (800568)
          [/home/kmarsden/testjars/derbyclient.jar] 10.4.2.1 - (800577)

          and 10.4 derbyTesting.jar (800577)

          I get the following failures runnng just jdbcapi.XATransactionTest
          .
          testGlobalXIDinTransactionTable used 221 ms .
          testXATransactionTimeout used 35838 ms .
          testXAExceptionErrorCodeOnSQLExceptionDerby4141 used 18 ms .
          testGlobalXIDinTransactionTable used 210 ms E.
          testXATransactionTimeout used 19 ms E.
          testXAExceptionErrorCodeOnSQLExceptionDerby4141 used 11 ms Ejava.sql.SQLException: Connection authentication failure occurred. Reason: Invalid authentication..
          at org.apache.derby.impl.drda.NetworkServerControlImpl.throwSQLException(NetworkServerControlImpl.java:3238)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(NetworkServerControlImpl.java:3175)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(NetworkServerControlImpl.java:1848)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.wrapSQLError(NetworkServerControlImpl.java:3743)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(NetworkServerControlImpl.java:2718)
          at org.apache.derby.impl.drda.NetworkServerControlImpl.shutdown(NetworkServerControlImpl.java:991)
          at org.apache.derby.drda.NetworkServerControl.shutdown(NetworkServerControl.java:384)
          at org.apache.derbyTesting.junit.NetworkServerTestSetup.tearDown(NetworkServerTestSetup.java:372)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          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.framework.TestResult.runProtected(TestResult.java:124)
          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.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:23)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.framework.TestSuite.runTest(TestSuite.java:208)
          at junit.framework.TestSuite.run(TestSuite.java:203)
          at junit.textui.TestRunner.doRun(TestRunner.java:116)
          at junit.textui.TestRunner.start(TestRunner.java:172)
          at junit.textui.TestRunner.main(TestRunner.java:138)

          Time: 46.731
          There were 3 errors:
          1) testGlobalXIDinTransactionTable(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest)java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred. Reason: userid or password invalid.
          at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70)
          at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362)
          at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:149)
          at java.sql.DriverManager.getConnection(DriverManager.java:316)
          at java.sql.DriverManager.getConnection(DriverManager.java:297)
          at org.apache.derbyTesting.junit.DriverManagerConnector.getConnectionByAttributes(DriverManagerConnector.java:131)
          at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:91)
          at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43)
          at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1312)
          at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:419)
          at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:101)
          at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest.testGlobalXIDinTransactionTable(XATransactionTest.java:52)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
          at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:102)
          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: org.apache.derby.client.am.SqlException: Connection authentication failure occurred. Reason: userid or password invalid.
          at org.apache.derby.client.net.NetConnection.mapSecchkcd(NetConnection.java:1170)
          at org.apache.derby.client.net.NetConnection.securityCheckComplete(NetConnection.java:985)
          at org.apache.derby.client.net.NetConnectionReply.parseSECCHKRM(NetConnectionReply.java:610)
          at org.apache.derby.client.net.NetConnectionReply.parseSECCHKreply(NetConnectionReply.java:272)
          at org.apache.derby.client.net.NetConnectionReply.readSecurityCheck(NetConnectionReply.java:113)
          at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:822)
          at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:747)
          at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(NetConnection.java:568)
          at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:383)
          at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:218)
          at org.apache.derby.client.net.NetConnection40.<init>(NetConnection40.java:77)
          at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:269)
          at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:140)
          ... 41 more
          2) testXATransactionTimeout(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest)java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred. Reason: userid or password invalid.
          at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70)
          at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362)
          at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:149)
          at java.sql.DriverManager.getConnection(DriverManager.java:316)
          at java.sql.DriverManager.getConnection(DriverManager.java:297)
          at org.apache.derbyTesting.junit.DriverManagerConnector.getConnectionByAttributes(DriverManagerConnector.java:131)
          at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:91)
          at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43)
          at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1312)
          at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:419)
          at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:101)
          at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest.testXATransactionTimeout(XATransactionTest.java:179)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
          at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:102)
          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: org.apache.derby.client.am.SqlException: Connection authentication failure occurred. Reason: userid or password invalid.
          at org.apache.derby.client.net.NetConnection.mapSecchkcd(NetConnection.java:1170)
          at org.apache.derby.client.net.NetConnection.securityCheckComplete(NetConnection.java:985)
          at org.apache.derby.client.net.NetConnectionReply.parseSECCHKRM(NetConnectionReply.java:610)
          at org.apache.derby.client.net.NetConnectionReply.parseSECCHKreply(NetConnectionReply.java:272)
          at org.apache.derby.client.net.NetConnectionReply.readSecurityCheck(NetConnectionReply.java:113)
          at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:822)
          at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:747)
          at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(NetConnection.java:568)
          at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:383)
          at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:218)
          at org.apache.derby.client.net.NetConnection40.<init>(NetConnection40.java:77)
          at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:269)
          at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:140)
          ... 41 more
          3) testXAExceptionErrorCodeOnSQLExceptionDerby4141(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest)java.sql.SQLNonTransientConnectionException: The connection was refused because the database wombat was not found.
          at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70)
          at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362)
          at org.apache.derby.client.ClientPooledConnection.<init>(ClientPooledConnection.java:167)
          at org.apache.derby.client.ClientXAConnection.<init>(ClientXAConnection.java:48)
          at org.apache.derby.client.ClientXAConnection40.<init>(ClientXAConnection40.java:56)
          at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newClientXAConnection(ClientJDBCObjectFactoryImpl40.java:98)
          at org.apache.derby.jdbc.ClientXADataSource.getXAConnectionX(ClientXADataSource.java:88)
          at org.apache.derby.jdbc.ClientXADataSource.getXAConnection(ClientXADataSource.java:72)
          at org.apache.derby.jdbc.ClientXADataSource.getXAConnection(ClientXADataSource.java:65)
          at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest.testXAExceptionErrorCodeOnSQLExceptionDerby4141(XATransactionTest.java:285)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
          at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:102)
          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: org.apache.derby.client.am.DisconnectException: The connection was refused because the database wombat was not found.
          at org.apache.derby.client.net.NetConnectionReply.parseRDBNFNRM(NetConnectionReply.java:1010)
          at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(NetConnectionReply.java:436)
          at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(NetConnectionReply.java:294)
          at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(NetConnectionReply.java:121)
          at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:823)
          at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:747)
          at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(NetConnection.java:568)
          at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:383)
          at org.apache.derby.client.net.NetConnection.initialize(NetConnection.java:301)
          at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:285)
          at org.apache.derby.client.net.NetConnection40.<init>(NetConnection40.java:125)
          at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:320)
          at org.apache.derby.client.net.NetXAConnection.createNetConnection(NetXAConnection.java:269)
          at org.apache.derby.client.net.NetXAConnection.<init>(NetXAConnection.java:73)
          at org.apache.derby.client.ClientPooledConnection.getNetXAConnection(ClientPooledConnection.java:472)
          at org.apache.derby.client.ClientPooledConnection.<init>(ClientPooledConnection.java:161)
          ... 39 more

          FAILURES!!!
          Tests run: 6, Failures: 0, Errors: 3

          No mention of authentication failure in the derby.log. I didn't see Suran or Mamta mention this problem but it sounds vaguely familiar. I don't see any authentication set up in XATransactionTest.

          Show
          Kathey Marsden added a comment - Running on the latest on the 10.5 and 10.4 branches: [/home/kmarsden/testjars/derby.jar] 10.5.2.1 - (800568) [/home/kmarsden/testjars/derbytools.jar] 10.5.2.1 - (800568) [/home/kmarsden/testjars/derbynet.jar] 10.5.2.1 - (800568) [/home/kmarsden/testjars/derbyclient.jar] 10.4.2.1 - (800577) and 10.4 derbyTesting.jar (800577) I get the following failures runnng just jdbcapi.XATransactionTest . testGlobalXIDinTransactionTable used 221 ms . testXATransactionTimeout used 35838 ms . testXAExceptionErrorCodeOnSQLExceptionDerby4141 used 18 ms . testGlobalXIDinTransactionTable used 210 ms E. testXATransactionTimeout used 19 ms E. testXAExceptionErrorCodeOnSQLExceptionDerby4141 used 11 ms Ejava.sql.SQLException: Connection authentication failure occurred. Reason: Invalid authentication.. at org.apache.derby.impl.drda.NetworkServerControlImpl.throwSQLException(NetworkServerControlImpl.java:3238) at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(NetworkServerControlImpl.java:3175) at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(NetworkServerControlImpl.java:1848) at org.apache.derby.impl.drda.NetworkServerControlImpl.wrapSQLError(NetworkServerControlImpl.java:3743) at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(NetworkServerControlImpl.java:2718) at org.apache.derby.impl.drda.NetworkServerControlImpl.shutdown(NetworkServerControlImpl.java:991) at org.apache.derby.drda.NetworkServerControl.shutdown(NetworkServerControl.java:384) at org.apache.derbyTesting.junit.NetworkServerTestSetup.tearDown(NetworkServerTestSetup.java:372) at junit.extensions.TestSetup$1.protect(TestSetup.java:20) at junit.framework.TestResult.runProtected(TestResult.java:124) 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.framework.TestResult.runProtected(TestResult.java:124) 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.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:23) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.textui.TestRunner.doRun(TestRunner.java:116) at junit.textui.TestRunner.start(TestRunner.java:172) at junit.textui.TestRunner.main(TestRunner.java:138) Time: 46.731 There were 3 errors: 1) testGlobalXIDinTransactionTable(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest)java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred. Reason: userid or password invalid. at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70) at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362) at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:149) at java.sql.DriverManager.getConnection(DriverManager.java:316) at java.sql.DriverManager.getConnection(DriverManager.java:297) at org.apache.derbyTesting.junit.DriverManagerConnector.getConnectionByAttributes(DriverManagerConnector.java:131) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:91) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1312) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:419) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:101) at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest.testGlobalXIDinTransactionTable(XATransactionTest.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:102) 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: org.apache.derby.client.am.SqlException: Connection authentication failure occurred. Reason: userid or password invalid. at org.apache.derby.client.net.NetConnection.mapSecchkcd(NetConnection.java:1170) at org.apache.derby.client.net.NetConnection.securityCheckComplete(NetConnection.java:985) at org.apache.derby.client.net.NetConnectionReply.parseSECCHKRM(NetConnectionReply.java:610) at org.apache.derby.client.net.NetConnectionReply.parseSECCHKreply(NetConnectionReply.java:272) at org.apache.derby.client.net.NetConnectionReply.readSecurityCheck(NetConnectionReply.java:113) at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:822) at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:747) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(NetConnection.java:568) at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:383) at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:218) at org.apache.derby.client.net.NetConnection40.<init>(NetConnection40.java:77) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:269) at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:140) ... 41 more 2) testXATransactionTimeout(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest)java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred. Reason: userid or password invalid. at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70) at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362) at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:149) at java.sql.DriverManager.getConnection(DriverManager.java:316) at java.sql.DriverManager.getConnection(DriverManager.java:297) at org.apache.derbyTesting.junit.DriverManagerConnector.getConnectionByAttributes(DriverManagerConnector.java:131) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:91) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1312) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:419) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:101) at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest.testXATransactionTimeout(XATransactionTest.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:102) 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: org.apache.derby.client.am.SqlException: Connection authentication failure occurred. Reason: userid or password invalid. at org.apache.derby.client.net.NetConnection.mapSecchkcd(NetConnection.java:1170) at org.apache.derby.client.net.NetConnection.securityCheckComplete(NetConnection.java:985) at org.apache.derby.client.net.NetConnectionReply.parseSECCHKRM(NetConnectionReply.java:610) at org.apache.derby.client.net.NetConnectionReply.parseSECCHKreply(NetConnectionReply.java:272) at org.apache.derby.client.net.NetConnectionReply.readSecurityCheck(NetConnectionReply.java:113) at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:822) at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:747) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(NetConnection.java:568) at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:383) at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:218) at org.apache.derby.client.net.NetConnection40.<init>(NetConnection40.java:77) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:269) at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:140) ... 41 more 3) testXAExceptionErrorCodeOnSQLExceptionDerby4141(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest)java.sql.SQLNonTransientConnectionException: The connection was refused because the database wombat was not found. at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70) at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362) at org.apache.derby.client.ClientPooledConnection.<init>(ClientPooledConnection.java:167) at org.apache.derby.client.ClientXAConnection.<init>(ClientXAConnection.java:48) at org.apache.derby.client.ClientXAConnection40.<init>(ClientXAConnection40.java:56) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newClientXAConnection(ClientJDBCObjectFactoryImpl40.java:98) at org.apache.derby.jdbc.ClientXADataSource.getXAConnectionX(ClientXADataSource.java:88) at org.apache.derby.jdbc.ClientXADataSource.getXAConnection(ClientXADataSource.java:72) at org.apache.derby.jdbc.ClientXADataSource.getXAConnection(ClientXADataSource.java:65) at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest.testXAExceptionErrorCodeOnSQLExceptionDerby4141(XATransactionTest.java:285) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:102) 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: org.apache.derby.client.am.DisconnectException: The connection was refused because the database wombat was not found. at org.apache.derby.client.net.NetConnectionReply.parseRDBNFNRM(NetConnectionReply.java:1010) at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(NetConnectionReply.java:436) at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(NetConnectionReply.java:294) at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(NetConnectionReply.java:121) at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:823) at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:747) at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(NetConnection.java:568) at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:383) at org.apache.derby.client.net.NetConnection.initialize(NetConnection.java:301) at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:285) at org.apache.derby.client.net.NetConnection40.<init>(NetConnection40.java:125) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:320) at org.apache.derby.client.net.NetXAConnection.createNetConnection(NetXAConnection.java:269) at org.apache.derby.client.net.NetXAConnection.<init>(NetXAConnection.java:73) at org.apache.derby.client.ClientPooledConnection.getNetXAConnection(ClientPooledConnection.java:472) at org.apache.derby.client.ClientPooledConnection.<init>(ClientPooledConnection.java:161) ... 39 more FAILURES!!! Tests run: 6, Failures: 0, Errors: 3 No mention of authentication failure in the derby.log. I didn't see Suran or Mamta mention this problem but it sounds vaguely familiar. I don't see any authentication set up in XATransactionTest.
          Hide
          Kathey Marsden added a comment -

          Sorry, user error. I forgot I had a network server running on the machine.

          Show
          Kathey Marsden added a comment - Sorry, user error. I forgot I had a network server running on the machine.
          Hide
          Kathey Marsden added a comment -

          I believe this issue was caused by DERBY-4053. Now that that is fixed suites.All no longer hangs and the reported exception no longer occurs.

          Show
          Kathey Marsden added a comment - I believe this issue was caused by DERBY-4053 . Now that that is fixed suites.All no longer hangs and the reported exception no longer occurs.

            People

            • Assignee:
              Unassigned
              Reporter:
              Suran Jayathilaka
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development