Derby
  1. Derby
  2. DERBY-5686

multiple intermittent errors in nightly tests during DriverMgrAuthenticationTest test. reason: An SQL data change is not permitted for a read-only connection, user or database.

    Details

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

      Description

      8 errors in nightly test runs on 4/4/2012 against trunk, windows, ibm16, build 1310147 . Tests passed against same build, same machine on ibm15 and ibm17
      http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1310147-suites.All_diff.txt
      There were 8 errors:
      1) testNotFullAccessUsers(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
      at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setProperties(DatabasePropertyTestSetup.java:352)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setUp(DatabasePropertyTestSetup.java:268)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      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)
      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 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)
      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 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)
      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)
      Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source)
      at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source)
      ... 47 more
      2) testNotFullAccessUsers(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
      at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:294)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      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 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)
      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 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)
      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)
      Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source)
      at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source)
      ... 41 more
      3) testChangePasswordAndDatabasePropertiesOnly(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
      at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setProperties(DatabasePropertyTestSetup.java:352)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setUp(DatabasePropertyTestSetup.java:268)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      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)
      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 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)
      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 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)
      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)
      Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source)
      at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source)
      ... 47 more
      4) testChangePasswordAndDatabasePropertiesOnly(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
      at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:294)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      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 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)
      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 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)
      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)
      Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source)
      at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source)
      ... 41 more
      5) testGreekCharacters(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
      at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setProperties(DatabasePropertyTestSetup.java:352)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setUp(DatabasePropertyTestSetup.java:268)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      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)
      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 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)
      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 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)
      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)
      Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source)
      at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source)
      ... 47 more
      6) testGreekCharacters(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
      at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:294)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      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 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)
      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 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)
      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)
      Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source)
      at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source)
      ... 41 more
      7) testSystemShutdown(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
      at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setProperties(DatabasePropertyTestSetup.java:352)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setUp(DatabasePropertyTestSetup.java:268)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      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)
      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 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)
      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 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)
      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)
      Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source)
      at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source)
      ... 47 more
      8) testSystemShutdown(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
      at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source)
      at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:294)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      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 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)
      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 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)
      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)
      Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database.
      at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)
      at org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
      at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source)
      at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
      at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source)
      ... 41 more

      FAILURES!!!
      Tests run: 15467, Failures: 0, Errors: 8

      1. DERBY-5686_1.diff
        5 kB
        Myrna van Lunteren
      2. DERBY-5686_2.diff
        3 kB
        Myrna van Lunteren
      3. DERBY-5686_3.diff
        1 kB
        Kristian Waagan
      4. DERBY-5686_4.diff
        2 kB
        Myrna van Lunteren
      5. DERBY-5686_5.diff
        4 kB
        Myrna van Lunteren
      6. DERBY-5686_6.diff
        7 kB
        Myrna van Lunteren
      7. DERBY-5686_7.diff
        8 kB
        Myrna van Lunteren
      8. DERBY-5686-3a-add_missing_return.diff
        1 kB
        Kristian Waagan

        Issue Links

          Activity

          Hide
          Mike Matrigali added a comment -

          I spent some time looking at code and the 4/4/2012 error. I think we are seeing this error intermittently across builds and across jvms. I had
          been interpreting the read only message as something to do with left over files and maybe somehow booting on files being left over and still open
          on windows and then derby falling over to readonly. I see that the DriverMgrAuthenticationTest does as bunch of playing with readonly authentication,
          and now am wondering if the setup and/or tearDown routines are somehow getting a left over readonly connection and fail since they need
          write access.

          So for this case we have 8 errors and no failures, but each of the errors causes a whole test to just not run so more serious.
          From this test run we have the following from test run:
          (net)jdbcapi.AutoGenJDBC30Test.testUserGivenColumnsNull used 110 ms .
          (emb)jdbcapi.DriverMgrAuthenticationTest.testConnectShutdownAuthentication used 12453 ms .
          (emb)jdbcapi.DriverMgrAuthenticationTest.testUserFunctions used 1312 ms .
          (emb)jdbcapi.DriverMgrAuthenticationTest.testNotFullAccessUsers used 2594 ms .
          (emb)jdbcapi.DriverMgrAuthenticationTest.testChangePasswordAndDatabasePropertiesOnly used 1531 ms .

          (emb)jdbcapi.DriverMgrAuthenticationTest.testGreekCharacters used 6453 ms .
          (emb)jdbcapi.DriverMgrAuthenticationTest.testSystemShutdown used 6968 ms .
          (net)jdbcapi.DriverMgrAuthenticationTest.testConnectShutdownAuthentication used 7921 ms .
          (net)jdbcapi.DriverMgrAuthenticationTest.testUserFunctions used 2422 ms EEEEEEEE<assertDirectoryDeleted> attempt 1 left 2 files/dirs behind: 0=D:\jartest\JarResults.2012-04-05\ibm16_suites.All\system\singleUse\oneusec0\db.lck 1=D:\jartest\JarResults.2012-04-05\ibm16_suites.All\system\singleUse\oneusec0
          .
          (emb)jdbcapi.PoolDSAuthenticationTest.testConnectShutdownAuthentication used 19859 ms .

          It looks to me like network version of testUserFunctions ran and then we started having problems setting up to run
          network testNotFullAccessUsers, and all the rest of the tests left in the suite.

          The end of the testUserFunctions has the following code:
          // reset
          conn1 = openDefaultConnection("dan", ("dan" + PASSWORD_SUFFIX));
          setDatabaseProperty(
          "derby.database.defaultConnectionMode","fullAccess", conn1);
          setDatabaseProperty(
          "derby.connection.requireAuthentication","false", conn1);
          stmt = conn1.createStatement();
          assertUpdateCount(stmt, 0, "drop table APP.t1");
          conn1.commit();
          stmt.close();
          conn1.close();

          I am tempted to add a shutdown database here, and reopen default connection to just make sure the next test's setup has the right
          connection. Or could add some retry logic in the setup and teardown - not sure how easy that would be. But I don't want to mask a real code bug. I am wondering if there is any sort of connection caching that we are doing that
          might not be correctly clearing readonly access? I seem to remember past bugs where a reused connection would have some left over attribute
          sometimes that was not meant to be.

          I read the documentation and it doesn't explicitly say so, but it doesn't say not - so I assume that setting these database properties are
          supposed to take effect immediately. So my assumptions on derby correct behavior would be, but would appreciate opinions of those
          with authentication expertise:

          1) existing connections don't change their access authentication
          2) new connections initiated after the commit of the database properties should pick up new default authentication.

          The DatabasePropertyTestSetup.setUp code is going to use a connection that was produced from a getConnection() call which will use
          existing test connection if it exists.

          Of course this would be all easier to understand if I could reproduce, but I have not been able to in my environment so this is all from
          looking at static test results and the code. Any opinions on next steps are appreciated.

          Show
          Mike Matrigali added a comment - I spent some time looking at code and the 4/4/2012 error. I think we are seeing this error intermittently across builds and across jvms. I had been interpreting the read only message as something to do with left over files and maybe somehow booting on files being left over and still open on windows and then derby falling over to readonly. I see that the DriverMgrAuthenticationTest does as bunch of playing with readonly authentication, and now am wondering if the setup and/or tearDown routines are somehow getting a left over readonly connection and fail since they need write access. So for this case we have 8 errors and no failures, but each of the errors causes a whole test to just not run so more serious. From this test run we have the following from test run: (net)jdbcapi.AutoGenJDBC30Test.testUserGivenColumnsNull used 110 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testConnectShutdownAuthentication used 12453 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testUserFunctions used 1312 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testNotFullAccessUsers used 2594 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testChangePasswordAndDatabasePropertiesOnly used 1531 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testGreekCharacters used 6453 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testSystemShutdown used 6968 ms . (net)jdbcapi.DriverMgrAuthenticationTest.testConnectShutdownAuthentication used 7921 ms . (net)jdbcapi.DriverMgrAuthenticationTest.testUserFunctions used 2422 ms EEEEEEEE<assertDirectoryDeleted> attempt 1 left 2 files/dirs behind: 0=D:\jartest\JarResults.2012-04-05\ibm16_suites.All\system\singleUse\oneusec0\db.lck 1=D:\jartest\JarResults.2012-04-05\ibm16_suites.All\system\singleUse\oneusec0 . (emb)jdbcapi.PoolDSAuthenticationTest.testConnectShutdownAuthentication used 19859 ms . It looks to me like network version of testUserFunctions ran and then we started having problems setting up to run network testNotFullAccessUsers, and all the rest of the tests left in the suite. The end of the testUserFunctions has the following code: // reset conn1 = openDefaultConnection("dan", ("dan" + PASSWORD_SUFFIX)); setDatabaseProperty( "derby.database.defaultConnectionMode","fullAccess", conn1); setDatabaseProperty( "derby.connection.requireAuthentication","false", conn1); stmt = conn1.createStatement(); assertUpdateCount(stmt, 0, "drop table APP.t1"); conn1.commit(); stmt.close(); conn1.close(); I am tempted to add a shutdown database here, and reopen default connection to just make sure the next test's setup has the right connection. Or could add some retry logic in the setup and teardown - not sure how easy that would be. But I don't want to mask a real code bug. I am wondering if there is any sort of connection caching that we are doing that might not be correctly clearing readonly access? I seem to remember past bugs where a reused connection would have some left over attribute sometimes that was not meant to be. I read the documentation and it doesn't explicitly say so, but it doesn't say not - so I assume that setting these database properties are supposed to take effect immediately. So my assumptions on derby correct behavior would be, but would appreciate opinions of those with authentication expertise: 1) existing connections don't change their access authentication 2) new connections initiated after the commit of the database properties should pick up new default authentication. The DatabasePropertyTestSetup.setUp code is going to use a connection that was produced from a getConnection() call which will use existing test connection if it exists. Of course this would be all easier to understand if I could reproduce, but I have not been able to in my environment so this is all from looking at static test results and the code. Any opinions on next steps are appreciated.
          Hide
          Mike Matrigali added a comment -

          This issue may or may not be related to DERBY-5572 DERBY-5572 is getting userid-password errors instead of readonly. But if problem is that a connection is being used that has leftover attributes from the test, then they could be same issue.

          Show
          Mike Matrigali added a comment - This issue may or may not be related to DERBY-5572 DERBY-5572 is getting userid-password errors instead of readonly. But if problem is that a connection is being used that has leftover attributes from the test, then they could be same issue.
          Hide
          Mike Matrigali added a comment -

          I think this is the same issue, though shows different tests failing and only 4 errors. failed windows, ibm16, build 1308644, 4/2/2012
          http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1308644-suites.All_diff.txt

          1) testSystemShutdown(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
          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.EmbedStatement.executeStatement(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
          at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1297)
          at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setUp(AuthenticationTest.java:192)
          at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113)
          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)
          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 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)
          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)
          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 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)
          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)
          Caused by: java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
          at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)
          ... 63 more
          Caused by: ERROR 25502: An SQL data change is not permitted for a read-only connection, user or database.
          at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
          at org.apache.derby.impl.sql.conn.GenericAuthorizer.authorize(Unknown Source)
          at org.apache.derby.exe.ac0249415ax0136x76efxea75xffff977260360.g0(Unknown Source)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
          at org.apache.derby.impl.services.reflect.ReflectMethod.invoke(Unknown Source)
          at org.apache.derby.impl.sql.execute.CallStatementResultSet.open(Unknown Source)
          at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source)
          at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
          ... 57 more
          2) testSystemShutdown(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
          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.EmbedStatement.executeStatement(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source)
          at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:294)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          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 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)
          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)
          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 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)
          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)
          Caused by: java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
          at <unknown class>.<unknown method>(Unknown Source)
          ... 55 more
          Caused by: ERROR 25502: An SQL data change is not permitted for a read-only connection, user or database.
          at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
          at org.apache.derby.impl.sql.conn.GenericAuthorizer.authorize(Unknown Source)
          at org.apache.derby.exe.acfb4d815dx0136x76efxea75xffff977260360.g0(Unknown Source)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
          at org.apache.derby.impl.services.reflect.ReflectMethod.invoke(Unknown Source)
          at org.apache.derby.impl.sql.execute.CallStatementResultSet.open(Unknown Source)
          at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source)
          at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
          ... 49 more
          3) testSystemShutdown(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred. Reason: Invalid authentication..
          at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
          at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
          at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
          at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
          at java.sql.DriverManager.getConnection(DriverManager.java:379)
          at java.sql.DriverManager.getConnection(DriverManager.java:354)
          at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:100)
          at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:67)
          at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43)
          at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1633)
          at org.apache.derbyTesting.junit.BaseJDBCTestSetup.getConnection(BaseJDBCTestSetup.java:72)
          at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:280)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          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)
          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 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)
          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)
          Caused by: java.sql.SQLException: Connection authentication failure occurred. Reason: Invalid authentication..
          at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)
          ... 53 more
          4) testSystemShutdown(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred. Reason: Invalid authentication..
          at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
          at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
          at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
          at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
          at java.sql.DriverManager.getConnection(DriverManager.java:379)
          at java.sql.DriverManager.getConnection(DriverManager.java:354)
          at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:100)
          at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:67)
          at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43)
          at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1633)
          at org.apache.derbyTesting.junit.BaseJDBCTestSetup.getConnection(BaseJDBCTestSetup.java:72)
          at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:280)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          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 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)
          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)
          Caused by: java.sql.SQLException: Connection authentication failure occurred. Reason: Invalid authentication..
          at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
          at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)
          ... 48 more
          There was 1 failure:
          1) DriverMgrAuthenticationTestjunit.framework.AssertionFailedError: Failed to delete 14 files (root=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf): D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c10.dat (isDir=false, canRead=true, canWrite=true, size=20480), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c180.dat (isDir=false, canRead=true, canWrite=true, size=36864), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c191.dat (isDir=false, canRead=true, canWrite=true, size=16384), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c20.dat (isDir=false, canRead=true, canWrite=true, size=32768), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c51.dat (isDir=false, canRead=true, canWrite=true, size=16384), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c60.dat (isDir=false, canRead=true, canWrite=true, size=12288), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c71.dat (isDir=false, canRead=true, canWrite=true, size=8192), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c90.dat (isDir=false, canRead=true, canWrite=true, size=24576), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ca1.dat (isDir=false, canRead=true, canWrite=true, size=24576), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cc0.dat (isDir=false, canRead=true, canWrite=true, size=8192), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cd1.dat (isDir=false, canRead=true, canWrite=true, size=8192), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ce1.dat (isDir=false, canRead=true, canWrite=true, size=8192), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0 (isDir=true, canRead=true, canWrite=true, size=0), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf (isDir=true, canRead=true, canWrite=true, size=0)
          at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertDirectoryDeleted(BaseJDBCTestCase.java:1491)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup.java:120)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.access$000(DropDatabaseSetup.java:35)
          at org.apache.derbyTesting.junit.DropDatabaseSetup$1.run(DropDatabaseSetup.java:106)
          at java.security.AccessController.doPrivileged(AccessController.java:202)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:103)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:99)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDatabase(DropDatabaseSetup.java:92)
          at org.apache.derbyTesting.junit.DropDatabaseSetup.tearDown(DropDatabaseSetup.java:78)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          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)

          FAILURES!!!
          Tests run: 15471, Failures: 1, Errors: 4

          Here is the output from when the test failed:
          (net)jdbcapi.AutoGenJDBC30Test.testUserGivenColumnsNull used 94 ms .
          (emb)jdbcapi.DriverMgrAuthenticationTest.testConnectShutdownAuthentication used 27905 ms .
          (emb)jdbcapi.DriverMgrAuthenticationTest.testUserFunctions used 2469 ms .
          (emb)jdbcapi.DriverMgrAuthenticationTest.testNotFullAccessUsers used 765 ms .
          (emb)jdbcapi.DriverMgrAuthenticationTest.testChangePasswordAndDatabasePropertiesOnly used 1000 ms .

          (emb)jdbcapi.DriverMgrAuthenticationTest.testGreekCharacters used 7656 ms .
          (emb)jdbcapi.DriverMgrAuthenticationTest.testSystemShutdown java.io.FileNotFoundException: system\singleUse\oneusebf\db.lck (Access is denied.)
          at java.io.FileInputStream.open(Native Method)
          at java.io.FileInputStream.<init>(FileInputStream.java:137)
          at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.copySingleFile(PrivilegedFileOpsForTests.java:304)
          at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.recursiveCopy(PrivilegedFileOpsForTests.java:276)
          at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.access$000(PrivilegedFileOpsForTests.java:49)
          at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests$8.run(PrivilegedFileOpsForTests.java:235)
          at java.security.AccessController.doPrivileged(AccessController.java:251)
          at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.copy(PrivilegedFileOpsForTests.java:233)
          at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:137)
          at junit.framework.TestResult$1.protect(TestResult.java:106)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.framework.TestResult.run(TestResult.java:109)
          at junit.framework.TestCase.run(TestCase.java:120)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.textui.TestRunner.doRun(TestRunner.java:121)
          at junit.textui.TestRunner.start(TestRunner.java:185)
          at junit.textui.TestRunner.main(TestRunner.java:143)
          used 1484 ms EEEE<assertDirectoryDeleted> attempt 1 left 15 files/dirs behind: 0=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\db.lck 1=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c10.dat 2=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c180.dat 3=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c191.dat 4=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c20.dat 5=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c51.dat 6=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c60.dat 7=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c71.dat 8=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c90.dat 9=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ca1.dat 10=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cc0.dat 11=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cd1.dat 12=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ce1.dat 13=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0 14=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf
          <assertDirectoryDeleted> attempt 2 left 14 files/dirs behind: 0=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c10.dat 1=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c180.dat 2=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c191.dat 3=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c20.dat 4=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c51.dat 5=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c60.dat 6=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c71.dat 7=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c90.dat 8=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ca1.dat 9=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cc0.dat 10=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cd1.dat 11=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ce1.dat 12=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0 13=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf
          <assertDirectoryDeleted> attempt 3 left 14 files/dirs behind: 0=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c10.dat 1=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c180.dat 2=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c191.dat 3=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c20.dat 4=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c51.dat 5=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c60.dat 6=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c71.dat 7=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c90.dat 8=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ca1.dat 9=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cc0.dat 10=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cd1.dat 11=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ce1.dat 12=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0 13=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf
          <assertDirectoryDeleted> attempt 4 left 14 files/dirs behind: 0=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c10.dat 1=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c180.dat 2=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c191.dat 3=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c20.dat 4=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c51.dat 5=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c60.dat 6=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c71.dat 7=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c90.dat 8=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ca1.dat 9=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cc0.dat 10=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cd1.dat 11=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ce1.dat 12=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0 13=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf
          F.
          (net)jdbcapi.DriverMgrAuthenticationTest.testConnectShutdownAuthentication used 4625 ms .
          (net)jdbcapi.DriverMgrAuthenticationTest.testUserFunctions used 937 ms .
          (net)jdbcapi.DriverMgrAuthenticationTest.testNotFullAccessUsers used 1188 ms .
          (net)jdbcapi.DriverMgrAuthenticationTest.testChangePasswordAndDatabasePropertiesOnly used 578 ms .
          (net)jdbcapi.DriverMgrAuthenticationTest.testGreekCharacters used 2219 ms .
          (net)jdbcapi.DriverMgrAuthenticationTest.testSystemShutdown used 1188 ms .
          (emb)jdbcapi.PoolDSAuthenticationTest.testConnectShutdownAuthentication used 6391 ms .

          Show
          Mike Matrigali added a comment - I think this is the same issue, though shows different tests failing and only 4 errors. failed windows, ibm16, build 1308644, 4/2/2012 http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1308644-suites.All_diff.txt 1) testSystemShutdown(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database. 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.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source) at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1297) at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setUp(AuthenticationTest.java:192) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113) 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) 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 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) 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) 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 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) 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) Caused by: java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) ... 63 more Caused by: ERROR 25502: An SQL data change is not permitted for a read-only connection, user or database. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.sql.conn.GenericAuthorizer.authorize(Unknown Source) at org.apache.derby.exe.ac0249415ax0136x76efxea75xffff977260360.g0(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at org.apache.derby.impl.services.reflect.ReflectMethod.invoke(Unknown Source) at org.apache.derby.impl.sql.execute.CallStatementResultSet.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) ... 57 more 2) testSystemShutdown(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database. 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.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source) at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:294) at junit.extensions.TestSetup$1.protect(TestSetup.java:22) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) 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 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) 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) 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 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) 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) Caused by: java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database. at <unknown class>.<unknown method>(Unknown Source) ... 55 more Caused by: ERROR 25502: An SQL data change is not permitted for a read-only connection, user or database. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.sql.conn.GenericAuthorizer.authorize(Unknown Source) at org.apache.derby.exe.acfb4d815dx0136x76efxea75xffff977260360.g0(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at org.apache.derby.impl.services.reflect.ReflectMethod.invoke(Unknown Source) at org.apache.derby.impl.sql.execute.CallStatementResultSet.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) ... 49 more 3) testSystemShutdown(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred. Reason: Invalid authentication.. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source) at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:379) at java.sql.DriverManager.getConnection(DriverManager.java:354) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:100) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:67) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1633) at org.apache.derbyTesting.junit.BaseJDBCTestSetup.getConnection(BaseJDBCTestSetup.java:72) at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:280) at junit.extensions.TestSetup$1.protect(TestSetup.java:22) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) 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) 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 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) 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) Caused by: java.sql.SQLException: Connection authentication failure occurred. Reason: Invalid authentication.. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) ... 53 more 4) testSystemShutdown(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred. Reason: Invalid authentication.. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source) at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:379) at java.sql.DriverManager.getConnection(DriverManager.java:354) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:100) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:67) at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1633) at org.apache.derbyTesting.junit.BaseJDBCTestSetup.getConnection(BaseJDBCTestSetup.java:72) at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:280) at junit.extensions.TestSetup$1.protect(TestSetup.java:22) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) 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 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) 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) Caused by: java.sql.SQLException: Connection authentication failure occurred. Reason: Invalid authentication.. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) ... 48 more There was 1 failure: 1) DriverMgrAuthenticationTestjunit.framework.AssertionFailedError: Failed to delete 14 files (root=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf): D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c10.dat (isDir=false, canRead=true, canWrite=true, size=20480), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c180.dat (isDir=false, canRead=true, canWrite=true, size=36864), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c191.dat (isDir=false, canRead=true, canWrite=true, size=16384), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c20.dat (isDir=false, canRead=true, canWrite=true, size=32768), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c51.dat (isDir=false, canRead=true, canWrite=true, size=16384), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c60.dat (isDir=false, canRead=true, canWrite=true, size=12288), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c71.dat (isDir=false, canRead=true, canWrite=true, size=8192), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c90.dat (isDir=false, canRead=true, canWrite=true, size=24576), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ca1.dat (isDir=false, canRead=true, canWrite=true, size=24576), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cc0.dat (isDir=false, canRead=true, canWrite=true, size=8192), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cd1.dat (isDir=false, canRead=true, canWrite=true, size=8192), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ce1.dat (isDir=false, canRead=true, canWrite=true, size=8192), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0 (isDir=true, canRead=true, canWrite=true, size=0), D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf (isDir=true, canRead=true, canWrite=true, size=0) at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertDirectoryDeleted(BaseJDBCTestCase.java:1491) at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup.java:120) at org.apache.derbyTesting.junit.DropDatabaseSetup.access$000(DropDatabaseSetup.java:35) at org.apache.derbyTesting.junit.DropDatabaseSetup$1.run(DropDatabaseSetup.java:106) at java.security.AccessController.doPrivileged(AccessController.java:202) at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:103) at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:99) at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDatabase(DropDatabaseSetup.java:92) at org.apache.derbyTesting.junit.DropDatabaseSetup.tearDown(DropDatabaseSetup.java:78) at junit.extensions.TestSetup$1.protect(TestSetup.java:22) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) 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) FAILURES!!! Tests run: 15471, Failures: 1, Errors: 4 Here is the output from when the test failed: (net)jdbcapi.AutoGenJDBC30Test.testUserGivenColumnsNull used 94 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testConnectShutdownAuthentication used 27905 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testUserFunctions used 2469 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testNotFullAccessUsers used 765 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testChangePasswordAndDatabasePropertiesOnly used 1000 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testGreekCharacters used 7656 ms . (emb)jdbcapi.DriverMgrAuthenticationTest.testSystemShutdown java.io.FileNotFoundException: system\singleUse\oneusebf\db.lck (Access is denied.) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:137) at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.copySingleFile(PrivilegedFileOpsForTests.java:304) at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.recursiveCopy(PrivilegedFileOpsForTests.java:276) at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.access$000(PrivilegedFileOpsForTests.java:49) at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests$8.run(PrivilegedFileOpsForTests.java:235) at java.security.AccessController.doPrivileged(AccessController.java:251) at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.copy(PrivilegedFileOpsForTests.java:233) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:137) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.textui.TestRunner.doRun(TestRunner.java:121) at junit.textui.TestRunner.start(TestRunner.java:185) at junit.textui.TestRunner.main(TestRunner.java:143) used 1484 ms EEEE<assertDirectoryDeleted> attempt 1 left 15 files/dirs behind: 0=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\db.lck 1=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c10.dat 2=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c180.dat 3=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c191.dat 4=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c20.dat 5=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c51.dat 6=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c60.dat 7=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c71.dat 8=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c90.dat 9=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ca1.dat 10=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cc0.dat 11=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cd1.dat 12=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ce1.dat 13=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0 14=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf <assertDirectoryDeleted> attempt 2 left 14 files/dirs behind: 0=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c10.dat 1=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c180.dat 2=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c191.dat 3=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c20.dat 4=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c51.dat 5=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c60.dat 6=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c71.dat 7=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c90.dat 8=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ca1.dat 9=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cc0.dat 10=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cd1.dat 11=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ce1.dat 12=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0 13=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf <assertDirectoryDeleted> attempt 3 left 14 files/dirs behind: 0=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c10.dat 1=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c180.dat 2=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c191.dat 3=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c20.dat 4=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c51.dat 5=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c60.dat 6=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c71.dat 7=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c90.dat 8=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ca1.dat 9=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cc0.dat 10=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cd1.dat 11=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ce1.dat 12=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0 13=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf <assertDirectoryDeleted> attempt 4 left 14 files/dirs behind: 0=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c10.dat 1=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c180.dat 2=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c191.dat 3=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c20.dat 4=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c51.dat 5=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c60.dat 6=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c71.dat 7=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\c90.dat 8=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ca1.dat 9=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cc0.dat 10=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\cd1.dat 11=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0\ce1.dat 12=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf\seg0 13=D:\jartest\JarResults.2012-04-02\ibm16_suites.All\system\singleUse\oneusebf F. (net)jdbcapi.DriverMgrAuthenticationTest.testConnectShutdownAuthentication used 4625 ms . (net)jdbcapi.DriverMgrAuthenticationTest.testUserFunctions used 937 ms . (net)jdbcapi.DriverMgrAuthenticationTest.testNotFullAccessUsers used 1188 ms . (net)jdbcapi.DriverMgrAuthenticationTest.testChangePasswordAndDatabasePropertiesOnly used 578 ms . (net)jdbcapi.DriverMgrAuthenticationTest.testGreekCharacters used 2219 ms . (net)jdbcapi.DriverMgrAuthenticationTest.testSystemShutdown used 1188 ms . (emb)jdbcapi.PoolDSAuthenticationTest.testConnectShutdownAuthentication used 6391 ms .
          Hide
          Myrna van Lunteren added a comment -

          Attaching a patch which modifies DatabasePropertyTestSetup to catch SQLSTATE 25502 in the teardown method; and gather some info and print it out, and then close the current connection, and retry the same clearing of properties with a new connection.

          Hopefully this will clear the problem, if not, at least it will give us a bit more insight in the state of the connection when we see this.

          Patch ready for review.

          Show
          Myrna van Lunteren added a comment - Attaching a patch which modifies DatabasePropertyTestSetup to catch SQLSTATE 25502 in the teardown method; and gather some info and print it out, and then close the current connection, and retry the same clearing of properties with a new connection. Hopefully this will clear the problem, if not, at least it will give us a bit more insight in the state of the connection when we see this. Patch ready for review.
          Hide
          Myrna van Lunteren added a comment -

          I committed my patch.
          If the error is not seen, it won't affect the run, and if it is seen in the teardown method of the DatabasePropertyTestSetup, we'll hopefully see some info.

          However, I don't think this will solve the issue - or at least not entirely, because it doesn't seem to be always the DatabasePropertyTestSetup that's involved, nor is it always 'SQL'. For instance, it can also be 'DDL' i.e. ERROR 25503 (instead of 25502), see the stacktrace of the first failure with weme 6.2 on 4/25 (http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/weme6.2/1330624-suites.All_diff.txt);
          1)
          testDropTableAfterUpgradeWithConstraint(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: DDL is not permitted for a read-only connection, user or database.
          at org.apache.derby.impl.jdbc.SQLExceptionFactory.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.EmbedStatement.executeStatement(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
          at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
          at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testDropTableAfterUpgradeWithConstraint(BasicSetup.java:286)
          at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:195)
          at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113)
          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 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)
          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)
          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 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)
          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 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)
          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 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)
          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 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)
          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 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)
          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 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 junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          Caused by: ERROR 25503: DDL is not permitted for a read-only connection, user or database.
          at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
          at org.apache.derby.impl.sql.conn.GenericAuthorizer.authorize(Unknown Source)
          at org.apache.derby.impl.sql.execute.GenericResultSetFactory.getDDLResultSet(Unknown Source)
          at org.apache.derby.impl.sql.execute.ConstantActionActivation.execute(Unknown Source)
          at org.apache.derby.impl.sql.GenericActivationHolder.execute(Unknown Source)
          at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source)
          at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
          ... 101 more
          ------------------------

          This however seems related to a java.io.FileNotFoundException on db.lck which is printed earlier in the output, but apparently not causing a failure:

          ------------------------
          (emb)upgradeTests.BasicSetup.testDropTableAfterUpgradeWithConstraint java.io.FileNotFoundException: system\singleUse\oneusecb\db.lck (A component of the path name does not exist)
          at java.io.FileInputStream.<init>(FileInputStream.java:55)
          at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.copySingleFile(PrivilegedFileOpsForTests.java:304)
          at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.recursiveCopy(PrivilegedFileOpsForTests.java:276)
          at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.access$000(PrivilegedFileOpsForTests.java:49)
          at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests$8.run(PrivilegedFileOpsForTests.java:235)
          at java.security.AccessController.doPrivileged(AccessController.java:255)
          at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.copy(PrivilegedFileOpsForTests.java:233)
          at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:137)
          at junit.framework.TestResult$1.protect(TestResult.java:106)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.framework.TestResult.run(TestResult.java:109)
          at junit.framework.TestCase.run(TestCase.java:120)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
          at junit.framework.TestResult.runProtected(TestResult.java:124)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.framework.TestSuite.runTest(TestSuite.java:230)
          at junit.framework.TestSuite.run(TestSuite.java:225)
          at junit.textui.TestRunner.doRun(TestRunner.java:121)
          at junit.textui.TestRunner.start(TestRunner.java:185)
          at junit.textui.TestRunner.main(TestRunner.java:143)
          ------------------------

          But we'll wait and see what happens.

          Show
          Myrna van Lunteren added a comment - I committed my patch. If the error is not seen, it won't affect the run, and if it is seen in the teardown method of the DatabasePropertyTestSetup, we'll hopefully see some info. However, I don't think this will solve the issue - or at least not entirely, because it doesn't seem to be always the DatabasePropertyTestSetup that's involved, nor is it always 'SQL'. For instance, it can also be 'DDL' i.e. ERROR 25503 (instead of 25502), see the stacktrace of the first failure with weme 6.2 on 4/25 ( http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/weme6.2/1330624-suites.All_diff.txt ); 1) testDropTableAfterUpgradeWithConstraint(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: DDL is not permitted for a read-only connection, user or database. at org.apache.derby.impl.jdbc.SQLExceptionFactory.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.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source) at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testDropTableAfterUpgradeWithConstraint(BasicSetup.java:286) at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:195) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113) 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 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) 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) 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 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) 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 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) 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 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) 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 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) 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 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) 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 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 junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) Caused by: ERROR 25503: DDL is not permitted for a read-only connection, user or database. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.sql.conn.GenericAuthorizer.authorize(Unknown Source) at org.apache.derby.impl.sql.execute.GenericResultSetFactory.getDDLResultSet(Unknown Source) at org.apache.derby.impl.sql.execute.ConstantActionActivation.execute(Unknown Source) at org.apache.derby.impl.sql.GenericActivationHolder.execute(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) ... 101 more ------------------------ This however seems related to a java.io.FileNotFoundException on db.lck which is printed earlier in the output, but apparently not causing a failure: ------------------------ (emb)upgradeTests.BasicSetup.testDropTableAfterUpgradeWithConstraint java.io.FileNotFoundException: system\singleUse\oneusecb\db.lck (A component of the path name does not exist) at java.io.FileInputStream.<init>(FileInputStream.java:55) at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.copySingleFile(PrivilegedFileOpsForTests.java:304) at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.recursiveCopy(PrivilegedFileOpsForTests.java:276) at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.access$000(PrivilegedFileOpsForTests.java:49) at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests$8.run(PrivilegedFileOpsForTests.java:235) at java.security.AccessController.doPrivileged(AccessController.java:255) at org.apache.derbyTesting.functionTests.util.PrivilegedFileOpsForTests.copy(PrivilegedFileOpsForTests.java:233) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:137) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.textui.TestRunner.doRun(TestRunner.java:121) at junit.textui.TestRunner.start(TestRunner.java:185) at junit.textui.TestRunner.main(TestRunner.java:143) ------------------------ But we'll wait and see what happens.
          Hide
          Myrna van Lunteren added a comment -

          We did not hit the error during DatabasePropertyTestSetup.teardown, so I don't know whether we now would get more useful output, but we did hit another occurrence - this time during DatabasePropertyTestSetup.setUp()- see:
          http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm17/1332036-suites.All_diff.txt

          The stack of the first failure:
          ---------------------------
          1) testEmbeddedAttributes(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
          at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
          at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
          at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source)
          at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setProperties(DatabasePropertyTestSetup.java:392)
          at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setUp(DatabasePropertyTestSetup.java:272)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          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)
          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)
          Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database.
          at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
          at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)
          at org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown Source)
          at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
          at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source)
          at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source)
          at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
          at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source)
          ... 29 more

          As happens sometimes, there was no actual 'fail' directory for this; the only fail dirs created were for the subsequent jdbcapi.Derby2017LayerATest failures which report the DDL read-only message (SQLState Error 25503). I think those failures are likely later - the first occurrence is the .SQLState Error 25502.

          I am attaching a patch - DERBY-5686_2.diff which tries to catch this error during setUp by adding similar code as was added for the teardown() to the setProperties method.

          Review is welcome, otherwise I'll commit this in a couple of hours.

          Show
          Myrna van Lunteren added a comment - We did not hit the error during DatabasePropertyTestSetup.teardown, so I don't know whether we now would get more useful output, but we did hit another occurrence - this time during DatabasePropertyTestSetup.setUp()- see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm17/1332036-suites.All_diff.txt The stack of the first failure: --------------------------- 1) testEmbeddedAttributes(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverTest)java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database. at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source) at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source) at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setProperties(DatabasePropertyTestSetup.java:392) at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setUp(DatabasePropertyTestSetup.java:272) at junit.extensions.TestSetup$1.protect(TestSetup.java:20) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) 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) 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) Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database. at org.apache.derby.client.am.Statement.completeExecute(Unknown Source) at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source) at org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown Source) at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source) at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source) at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source) at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source) at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source) ... 29 more As happens sometimes, there was no actual 'fail' directory for this; the only fail dirs created were for the subsequent jdbcapi.Derby2017LayerATest failures which report the DDL read-only message (SQLState Error 25503). I think those failures are likely later - the first occurrence is the .SQLState Error 25502. I am attaching a patch - DERBY-5686 _2.diff which tries to catch this error during setUp by adding similar code as was added for the teardown() to the setProperties method. Review is welcome, otherwise I'll commit this in a couple of hours.
          Hide
          Myrna van Lunteren added a comment -

          I committed the _2.diff patch with revision 1332484.

          Show
          Myrna van Lunteren added a comment - I committed the _2.diff patch with revision 1332484.
          Hide
          Myrna van Lunteren added a comment -

          Unfortunately, my changes weren't enough to make the test pass - see:
          http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm15/1332892-suites.All_diff.txt
          and
          http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1332892-suites.All_diff.txt
          The ibm 1.5 failure was in DatabasePropertyTestSetup.teardown(), but the new connection was also reported as readOnly, so retry was pointless. I'm not any further in understanding where it (the connection or the database?) was set to readOnly.
          One theory was that an earlier test did a setReadOnly and that this somehow propogated - jdbcapi.DataSourceTest and jdbcapi.J2EEDataSourceTest do this at some point - but in the ibm 1.5 failures, as in several earlier cases, those 2 tests either didn't run at all (e.g. with 1.7 jvm) or didn't run before the first failure.
          After the initial failure we see a host of other trouble such as invalid authentication errors.

          The ibm 1.6 failure shows that it did hit the additional code in DatabasePropertyTestSetup.setProperties, but unfortunately the code I added to do conn.close() failed, because the transaction is still open (causing different failures than before, not helping matters).

          Show
          Myrna van Lunteren added a comment - Unfortunately, my changes weren't enough to make the test pass - see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm15/1332892-suites.All_diff.txt and http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1332892-suites.All_diff.txt The ibm 1.5 failure was in DatabasePropertyTestSetup.teardown(), but the new connection was also reported as readOnly, so retry was pointless. I'm not any further in understanding where it (the connection or the database?) was set to readOnly. One theory was that an earlier test did a setReadOnly and that this somehow propogated - jdbcapi.DataSourceTest and jdbcapi.J2EEDataSourceTest do this at some point - but in the ibm 1.5 failures, as in several earlier cases, those 2 tests either didn't run at all (e.g. with 1.7 jvm) or didn't run before the first failure. After the initial failure we see a host of other trouble such as invalid authentication errors. The ibm 1.6 failure shows that it did hit the additional code in DatabasePropertyTestSetup.setProperties, but unfortunately the code I added to do conn.close() failed, because the transaction is still open (causing different failures than before, not helping matters).
          Hide
          Kristian Waagan added a comment -

          Attaching patch DERBY-5686_3, which modifies the logic in assertDirectoryDeleted to tolerate that the root directory for some reason gets unexpectedly deleted.
          Note that the method will still fail if the directory doesn't exist in the first iteration.

          Patch ready for review.

          FYI, I saw that one test failed because of the old logic in the ibm16 run Myrna referred to. The only file that couldn't be deleted was db.lck. The root directory wasn't listed as "undeletable". Probably db.lck was attempted deleted early on while Derby was still running, and assertDirectoryDeleted deleted all the other files. I'm guessing that Derby deleted the lock file as part of shutdown before assertDirectoryDeleted got around to delete the root directory. Removing the directory succeeded because it would have been empty at that point.

          Show
          Kristian Waagan added a comment - Attaching patch DERBY-5686 _3, which modifies the logic in assertDirectoryDeleted to tolerate that the root directory for some reason gets unexpectedly deleted. Note that the method will still fail if the directory doesn't exist in the first iteration. Patch ready for review. FYI, I saw that one test failed because of the old logic in the ibm16 run Myrna referred to. The only file that couldn't be deleted was db.lck. The root directory wasn't listed as "undeletable". Probably db.lck was attempted deleted early on while Derby was still running, and assertDirectoryDeleted deleted all the other files. I'm guessing that Derby deleted the lock file as part of shutdown before assertDirectoryDeleted got around to delete the root directory. Removing the directory succeeded because it would have been empty at that point.
          Hide
          Myrna van Lunteren added a comment -

          I'm attaching another patch which tries to finagle the retrying/catch info code. This is still debugging code, and may possibly be removed/adjusted again later. Ready for review.

          Show
          Myrna van Lunteren added a comment - I'm attaching another patch which tries to finagle the retrying/catch info code. This is still debugging code, and may possibly be removed/adjusted again later. Ready for review.
          Hide
          Myrna van Lunteren added a comment -

          Thanks for looking at this issue Kristian.
          +1 to implementing patch DERBY-5686_3.diff, it looks like a good improvement, although I think the error related to assertDirectoryDeleted is a result of the earlier failures, or at least a later issue...

          Show
          Myrna van Lunteren added a comment - Thanks for looking at this issue Kristian. +1 to implementing patch DERBY-5686 _3.diff, it looks like a good improvement, although I think the error related to assertDirectoryDeleted is a result of the earlier failures, or at least a later issue...
          Hide
          Kristian Waagan added a comment -

          Committed patch 3 to trunk with revision 1334313.

          Show
          Kristian Waagan added a comment - Committed patch 3 to trunk with revision 1334313.
          Hide
          Myrna van Lunteren added a comment -

          Unfortunately, the latest commit now causes a loop that we never break out of...
          This for instance is the end of console output from a recent unfinished (and hence not published) test run before I killed the process:
          --------------------------------
          (net)jdbcapi.InternationalConnectTest.testDriverManagerConnect used 13797 ms .
          (net)jdbcapi.InternationalConnectTest.testXADSConnect <assertDirectoryDeleted> attempt 1 left 1 files/dirs behind: 0=D:\jartest\JarResults.2012-05-07\ibm17_suites.All\system?\tmp
          <assertDirectoryDeleted> root directory unexpectedly gone - delayed, external or concurrent delete?
          <assertDirectoryDeleted> attempt 1 left 1 files/dirs behind: 0=D:\jartest\JarResults.2012-05-07\ibm17_suites.All\system?\tmp
          <assertDirectoryDeleted> root directory unexpectedly gone - delayed, external or concurrent delete?
          <assertDirectoryDeleted> attempt 1 left 1 files/dirs behind: 0=D:\jartest\JarResults.2012-05-07\ibm17_suites.All\system?\tmp
          <assertDirectoryDeleted> root directory unexpectedly gone - delayed, external or concurrent delete?
          [....etc...]
          --------------------------------
          Did we perhaps miss adding attempts++? I'm going to assume we did. I'll add a finally block...

          Show
          Myrna van Lunteren added a comment - Unfortunately, the latest commit now causes a loop that we never break out of... This for instance is the end of console output from a recent unfinished (and hence not published) test run before I killed the process: -------------------------------- (net)jdbcapi.InternationalConnectTest.testDriverManagerConnect used 13797 ms . (net)jdbcapi.InternationalConnectTest.testXADSConnect <assertDirectoryDeleted> attempt 1 left 1 files/dirs behind: 0=D:\jartest\JarResults.2012-05-07\ibm17_suites.All\system?\tmp <assertDirectoryDeleted> root directory unexpectedly gone - delayed, external or concurrent delete? <assertDirectoryDeleted> attempt 1 left 1 files/dirs behind: 0=D:\jartest\JarResults.2012-05-07\ibm17_suites.All\system?\tmp <assertDirectoryDeleted> root directory unexpectedly gone - delayed, external or concurrent delete? <assertDirectoryDeleted> attempt 1 left 1 files/dirs behind: 0=D:\jartest\JarResults.2012-05-07\ibm17_suites.All\system?\tmp <assertDirectoryDeleted> root directory unexpectedly gone - delayed, external or concurrent delete? [....etc...] -------------------------------- Did we perhaps miss adding attempts++? I'm going to assume we did. I'll add a finally block...
          Hide
          Myrna van Lunteren added a comment -

          committed adding a finally block with revision 1335820.

          Show
          Myrna van Lunteren added a comment - committed adding a finally block with revision 1335820.
          Hide
          Kristian Waagan added a comment -

          Thanks, Myrna.

          Sorry about that mistake. When I look at the code now, I believe I forgot a return-statement in the else-block (inside the catch-block).
          See patch 3a, which also backs out the addition of the finally-block. While the unconditional increment of attempts breaks the loop, it will cause the test/setup to fail because fl will always contain at least one element. I suppose Java lists '?' as the directory name because it has been deleted.

          Patch ready for review.

          Show
          Kristian Waagan added a comment - Thanks, Myrna. Sorry about that mistake. When I look at the code now, I believe I forgot a return-statement in the else-block (inside the catch-block). See patch 3a, which also backs out the addition of the finally-block. While the unconditional increment of attempts breaks the loop, it will cause the test/setup to fail because fl will always contain at least one element. I suppose Java lists '?' as the directory name because it has been deleted. Patch ready for review.
          Hide
          Myrna van Lunteren added a comment -

          Thanks for the explanation Kristian. +1 for committing your update.

          Show
          Myrna van Lunteren added a comment - Thanks for the explanation Kristian. +1 for committing your update.
          Hide
          Mike Matrigali added a comment -

          looks like the following is caused by retry logic not committing/aborting transaction before closing connection:
          http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm15/1335323-suites.All_diff.txt

          There were 2 errors:
          1) testInvalidAlgorithmName(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: Cannot close a connection while a transaction is still active.
          at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
          at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
          at org.apache.derby.client.am.Connection.closeResourcesX(Unknown Source)
          at org.apache.derby.client.am.Connection.closeX(Unknown Source)
          at org.apache.derby.client.net.NetConnection.closeX(Unknown Source)
          at org.apache.derby.client.am.Connection.close(Unknown Source)
          at org.apache.derby.client.net.NetConnection.close(Unknown Source)
          at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setProperties(DatabasePropertyTestSetup.java:372)
          at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setUp(DatabasePropertyTestSetup.java:272)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          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)
          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 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)
          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 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)
          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)
          Caused by: org.apache.derby.client.am.SqlException: Cannot close a connection while a transaction is still active.
          at org.apache.derby.client.am.Connection.checkForTransactionInProgress(Unknown Source)
          ... 51 more
          2) testInvalidAlgorithmName(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: Cannot close a connection while a transaction is still active.
          at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
          at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
          at org.apache.derby.client.am.Connection.closeResourcesX(Unknown Source)
          at org.apache.derby.client.am.Connection.closeX(Unknown Source)
          at org.apache.derby.client.net.NetConnection.closeX(Unknown Source)
          at org.apache.derby.client.am.Connection.close(Unknown Source)
          at org.apache.derby.client.net.NetConnection.close(Unknown Source)
          at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:303)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
          at junit.extensions.TestSetup.run(TestSetup.java:25)
          at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
          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 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)
          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 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)
          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)
          Caused by: org.apache.derby.client.am.SqlException: Cannot close a connection while a transaction is still active.
          at org.apache.derby.client.am.Connection.checkForTransactionInProgress(Unknown Source)
          ... 45 more

          Show
          Mike Matrigali added a comment - looks like the following is caused by retry logic not committing/aborting transaction before closing connection: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm15/1335323-suites.All_diff.txt There were 2 errors: 1) testInvalidAlgorithmName(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: Cannot close a connection while a transaction is still active. at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source) at org.apache.derby.client.am.Connection.closeResourcesX(Unknown Source) at org.apache.derby.client.am.Connection.closeX(Unknown Source) at org.apache.derby.client.net.NetConnection.closeX(Unknown Source) at org.apache.derby.client.am.Connection.close(Unknown Source) at org.apache.derby.client.net.NetConnection.close(Unknown Source) at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setProperties(DatabasePropertyTestSetup.java:372) at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.setUp(DatabasePropertyTestSetup.java:272) at junit.extensions.TestSetup$1.protect(TestSetup.java:20) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) 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) 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 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) 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 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) 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) Caused by: org.apache.derby.client.am.SqlException: Cannot close a connection while a transaction is still active. at org.apache.derby.client.am.Connection.checkForTransactionInProgress(Unknown Source) ... 51 more 2) testInvalidAlgorithmName(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: Cannot close a connection while a transaction is still active. at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source) at org.apache.derby.client.am.Connection.closeResourcesX(Unknown Source) at org.apache.derby.client.am.Connection.closeX(Unknown Source) at org.apache.derby.client.net.NetConnection.closeX(Unknown Source) at org.apache.derby.client.am.Connection.close(Unknown Source) at org.apache.derby.client.net.NetConnection.close(Unknown Source) at org.apache.derbyTesting.junit.DatabasePropertyTestSetup.tearDown(DatabasePropertyTestSetup.java:303) at junit.extensions.TestSetup$1.protect(TestSetup.java:22) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) 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 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) 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 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) 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) Caused by: org.apache.derby.client.am.SqlException: Cannot close a connection while a transaction is still active. at org.apache.derby.client.am.Connection.checkForTransactionInProgress(Unknown Source) ... 45 more
          Hide
          Myrna van Lunteren added a comment -

          Yes, that's why I put up my patch _4.diff on May 4...I was hoping for a review...
          But now I'm working on an alternative that catches error 25001 (Cannot close a connection while a transaction is still active) and does a commit then tries the close again. I want to run a full test suite with this change, so it'll take a while.
          Also I am working on some additional changes, because I think I've seen the error when it wasn't DatabasePropertyTestSetup that reported the db to be read-only.

          Show
          Myrna van Lunteren added a comment - Yes, that's why I put up my patch _4.diff on May 4...I was hoping for a review... But now I'm working on an alternative that catches error 25001 (Cannot close a connection while a transaction is still active) and does a commit then tries the close again. I want to run a full test suite with this change, so it'll take a while. Also I am working on some additional changes, because I think I've seen the error when it wasn't DatabasePropertyTestSetup that reported the db to be read-only.
          Hide
          Kristian Waagan added a comment -

          Committed patch 3a to trunk with revision 1336316.
          Sorry for polluting your issue, Myrna. I'll take a look at your next patch and see if I can contribute with anything of value.
          Do you mind filling out the environment-field of this issue?

          Show
          Kristian Waagan added a comment - Committed patch 3a to trunk with revision 1336316. Sorry for polluting your issue, Myrna. I'll take a look at your next patch and see if I can contribute with anything of value. Do you mind filling out the environment-field of this issue?
          Hide
          Myrna van Lunteren added a comment -

          Attaching another patch, which tries to address the situation where the retry logic in DatabasePropertyTestSetup would get an error. This also adds some code to cleanDatabaseTestSetup to catch tests leaving the connection in read-only state.

          Show
          Myrna van Lunteren added a comment - Attaching another patch, which tries to address the situation where the retry logic in DatabasePropertyTestSetup would get an error. This also adds some code to cleanDatabaseTestSetup to catch tests leaving the connection in read-only state.
          Hide
          Myrna van Lunteren added a comment -

          Thanks Kristian. The review comment wasn't necessarily directed at you...Plus I forgot to set the patch available flag.
          I feel better about the _5.diff and committed it already - revision 1336349.
          I updated the environment field of this issue.

          Show
          Myrna van Lunteren added a comment - Thanks Kristian. The review comment wasn't necessarily directed at you...Plus I forgot to set the patch available flag. I feel better about the _5.diff and committed it already - revision 1336349. I updated the environment field of this issue.
          Hide
          Myrna van Lunteren added a comment -

          Attaching a patch which tries to address another possible cause for the problems - perhaps the shutdown reports it's finished before it's actually completely shutdown.
          So this patch tries to check whether the db.lck and/or (for unix) dbex.lck file(s) are still present - if so, loop until they're gone, then continue to delete the database.

          This patch passed on my system (a different one from where the test failures are seen). Patch ready for review.

          Show
          Myrna van Lunteren added a comment - Attaching a patch which tries to address another possible cause for the problems - perhaps the shutdown reports it's finished before it's actually completely shutdown. So this patch tries to check whether the db.lck and/or (for unix) dbex.lck file(s) are still present - if so, loop until they're gone, then continue to delete the database. This patch passed on my system (a different one from where the test failures are seen). Patch ready for review.
          Hide
          Kristian Waagan added a comment -

          Thanks for updating the environment field, Myrna.

          Is patch 6 temporary, or is it intended as a permanent addition?

          Especially if the latter, I have a few questions and comments:
          o Are there cases where the lock files won't be removed for some reason?
          If yes, then there should be a timeout function, i.e. don't wait for more than X minutes.
          o You can avoid the boolean by using break, but with a timeout the loop will probably be rewritten anyway.
          o This patch masks an issue. I'd like it to print something if it has to wait, similar to what assertDirectoryDeleted does, as an incentive/reminder for fixing the real issue.
          I expect that with patch 6 committed, you shouldn't see any more output from assertDirectoryDeleted, except for in cases where there's a real bug with not closing file handles.

          The theory about the database shutdown now being complete is pretty much confirmed, since the file deletion logic has failed deleting db.lock and tmp. Both of these are supposed to be removed by Derby when it has shut down properly. I don't know if this is the reason for the read-only connections, but it will be good to rule that out.

          Do we know if the database goes read-only on boot, or if it turns read-only after being booted?

          Show
          Kristian Waagan added a comment - Thanks for updating the environment field, Myrna. Is patch 6 temporary, or is it intended as a permanent addition? Especially if the latter, I have a few questions and comments: o Are there cases where the lock files won't be removed for some reason? If yes, then there should be a timeout function, i.e. don't wait for more than X minutes. o You can avoid the boolean by using break, but with a timeout the loop will probably be rewritten anyway. o This patch masks an issue. I'd like it to print something if it has to wait, similar to what assertDirectoryDeleted does, as an incentive/reminder for fixing the real issue. I expect that with patch 6 committed, you shouldn't see any more output from assertDirectoryDeleted, except for in cases where there's a real bug with not closing file handles. The theory about the database shutdown now being complete is pretty much confirmed, since the file deletion logic has failed deleting db.lock and tmp. Both of these are supposed to be removed by Derby when it has shut down properly. I don't know if this is the reason for the read-only connections, but it will be good to rule that out. Do we know if the database goes read-only on boot, or if it turns read-only after being booted?
          Hide
          Myrna van Lunteren added a comment -

          Patch 6 was intended as a more permanent solution - if it did solve the problem...
          But we're still unclear on what causes derby to think the db is read-only.

          One part of the trouble is that this machine was running our nightly tests - meaning I only had a small time frame to debug/analyze/run experiments. I now switched the nightly runs to another machine, so I can debug/experiment better. At which point I don't need to commit to see the bad results, so the patch doesn't need to go in until we're sure it's fixing the trouble.

          To go into your questions (answers with a
          o Are there cases where the lock files won't be removed for some reason?
          If yes, then there should be a timeout function, i.e. don't wait for more than X minutes.
          a: I think this is what we're concerned about. Shutdown() should remove the lock files, but in this case it seems sometimes they're not removed, there seems to be a timing issue. The theory there is that if db.lck is present, we'll get an 25502 error.
          And you're right - there needs to be a timeout, possibly with some message.
          o You can avoid the boolean by using break, but with a timeout the loop will probably be rewritten anyway.
          a: You're right.
          o This patch masks an issue. I'd like it to print something if it has to wait, similar to what assertDirectoryDeleted does, as an incentive/reminder for fixing the real issue.
          a: Printing something makes sense, I'll work on that.

          q: Do we know if the database goes read-only on boot, or if it turns read-only after being booted?
          a: we don't know...It would be good to figure this out too...

          Show
          Myrna van Lunteren added a comment - Patch 6 was intended as a more permanent solution - if it did solve the problem... But we're still unclear on what causes derby to think the db is read-only. One part of the trouble is that this machine was running our nightly tests - meaning I only had a small time frame to debug/analyze/run experiments. I now switched the nightly runs to another machine, so I can debug/experiment better. At which point I don't need to commit to see the bad results, so the patch doesn't need to go in until we're sure it's fixing the trouble. To go into your questions (answers with a o Are there cases where the lock files won't be removed for some reason? If yes, then there should be a timeout function, i.e. don't wait for more than X minutes. a: I think this is what we're concerned about. Shutdown() should remove the lock files, but in this case it seems sometimes they're not removed, there seems to be a timing issue. The theory there is that if db.lck is present, we'll get an 25502 error. And you're right - there needs to be a timeout, possibly with some message. o You can avoid the boolean by using break, but with a timeout the loop will probably be rewritten anyway. a: You're right. o This patch masks an issue. I'd like it to print something if it has to wait, similar to what assertDirectoryDeleted does, as an incentive/reminder for fixing the real issue. a: Printing something makes sense, I'll work on that. q: Do we know if the database goes read-only on boot, or if it turns read-only after being booted? a: we don't know...It would be good to figure this out too...
          Hide
          Kathey Marsden added a comment -

          Although not well understood the connection between the tests and the , errors. At least the error that occurs in DERBY-5766 seems the same, so linking the issue

          Show
          Kathey Marsden added a comment - Although not well understood the connection between the tests and the , errors. At least the error that occurs in DERBY-5766 seems the same, so linking the issue
          Hide
          Myrna van Lunteren added a comment -

          Attaching another version of the patch which I think addresses Kristian's comments.

          Show
          Myrna van Lunteren added a comment - Attaching another version of the patch which I think addresses Kristian's comments.
          Hide
          Kathey Marsden added a comment -

          Hi Myrna, I think your patch from the 17th is safe to commit. I wonder where are the single use databases shutdown. It seems it is mostly those that relate to the failures in DERBY-5686

          Show
          Kathey Marsden added a comment - Hi Myrna, I think your patch from the 17th is safe to commit. I wonder where are the single use databases shutdown. It seems it is mostly those that relate to the failures in DERBY-5686
          Hide
          Myrna van Lunteren added a comment -

          The machine (results no longer published) was displaying the read-only trouble again on Friday night's run.
          I committed the patch _7.diff with revision 1346174.

          Show
          Myrna van Lunteren added a comment - The machine (results no longer published) was displaying the read-only trouble again on Friday night's run. I committed the patch _7.diff with revision 1346174.
          Hide
          Myrna van Lunteren added a comment -

          Despite the patch, we kept seeing various read-only errors.
          I finally had the disk swapped for a new one, and I deleted some space on the way - and now the problems are gone.
          I added back in the largeDataTest suite, to see what happens.

          On the whole, there have been a number of test failures reported that I think relate to the same issue. I'll mark all of those duplicates of this.

          Also, there have been some reports from users complaining about sudden read-only databases.
          It's something that can happen when the disk is full - in DERBY-555 Suresh hypothesized that this would happen if the db.lck file could not get created.
          https://issues.apache.org/jira/browse/DERBY-555?focusedCommentId=12320936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12320936
          But this is on booting the database. Was that the case with our failing test cases? Perhaps so, as in the case of it hitting through junit.DatabasePropertyTestSetup.

          Here are some relevant user questions:
          http://old.nabble.com/Derby-database-started-suddenly-in-READ-ONLY-mode-td33271488.html
          http://old.nabble.com/Derby-on-Tomcat-server-keeps-setting-itself-to-read-only-td23152838.html
          perhaps also http://forums.overclockers.co.uk/showthread.php?p=13923396 - maybe a case of running out of memory when tomcat is up?

          Show
          Myrna van Lunteren added a comment - Despite the patch, we kept seeing various read-only errors. I finally had the disk swapped for a new one, and I deleted some space on the way - and now the problems are gone. I added back in the largeDataTest suite, to see what happens. On the whole, there have been a number of test failures reported that I think relate to the same issue. I'll mark all of those duplicates of this. Also, there have been some reports from users complaining about sudden read-only databases. It's something that can happen when the disk is full - in DERBY-555 Suresh hypothesized that this would happen if the db.lck file could not get created. https://issues.apache.org/jira/browse/DERBY-555?focusedCommentId=12320936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12320936 But this is on booting the database. Was that the case with our failing test cases? Perhaps so, as in the case of it hitting through junit.DatabasePropertyTestSetup. Here are some relevant user questions: http://old.nabble.com/Derby-database-started-suddenly-in-READ-ONLY-mode-td33271488.html http://old.nabble.com/Derby-on-Tomcat-server-keeps-setting-itself-to-read-only-td23152838.html perhaps also http://forums.overclockers.co.uk/showthread.php?p=13923396 - maybe a case of running out of memory when tomcat is up?
          Hide
          Myrna van Lunteren added a comment -

          After adding the largeDataSuite again, the machine apparently got so maxed out in some way (memory? There ought to have been enough disk space...) that I couldn't log on to look at anything.
          Automatic reporting did see one occurrence of https://issues.apache.org/jira/browse/DERBY-5735.

          Then when I decided to boot the machine in order to stop the largeDataSuite again, it killed the disk.
          So, there is still a possibility that this occurs, but I don't want to spend more time on this now. It may even be 'by design' (based on the comments in DERBY-555), but it would at least be nice if derby could give a better message, because when you see 'read-only', the logical assumption is that there is something wrong with permissions or read-only settings somewhere.
          Unassigning myself.

          Show
          Myrna van Lunteren added a comment - After adding the largeDataSuite again, the machine apparently got so maxed out in some way (memory? There ought to have been enough disk space...) that I couldn't log on to look at anything. Automatic reporting did see one occurrence of https://issues.apache.org/jira/browse/DERBY-5735 . Then when I decided to boot the machine in order to stop the largeDataSuite again, it killed the disk. So, there is still a possibility that this occurs, but I don't want to spend more time on this now. It may even be 'by design' (based on the comments in DERBY-555 ), but it would at least be nice if derby could give a better message, because when you see 'read-only', the logical assumption is that there is something wrong with permissions or read-only settings somewhere. Unassigning myself.
          Hide
          Kathey Marsden added a comment -

          Taking off of High Value Fix per Myrna's comments depriortizing the issue. The better error reporting she recommends will still be on the High Value Fix list in the form of DERBY-5686

          Show
          Kathey Marsden added a comment - Taking off of High Value Fix per Myrna's comments depriortizing the issue. The better error reporting she recommends will still be on the High Value Fix list in the form of DERBY-5686

            People

            • Assignee:
              Unassigned
              Reporter:
              Mike Matrigali
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Development