Derby
  1. Derby
  2. DERBY-1757

checkDataSource30 produces no output, most likely hangs

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.2.1.6
    • Fix Version/s: 10.2.1.6
    • Component/s: Test
    • Labels:
      None
    • Environment:
      Seen both on

      JVM: Sun JDK 6 (build 1.6.0-rc-b95)
      OS: Solaris 10 (sparc)

      and

      JVM: Sun JDK 5 (1.5.0_04)
      OS: RHEL 4
    • Bug behavior facts:
      Regression Test Failure

      Description

      Seen while testing the 10.2.1.0 beta, in two different environments.

      Test produces no output, most likely it hangs and is killed after 1 hour.

                      • Diff file derbyall/derbynetclientmats/DerbyNetClient/derbynetmats/jdk14/checkDataSource30.diff
          • Start: checkDataSource30 jdk1.5.0_04 DerbyNetClient derbynetmats:jdk14 2006-08-15 01:21:15 ***
            711 del
            < By default, autocommit is true for a connection
            < Default holdability for a connection is HOLD_CURSORS_OVER_COMMIT
            < CONNECTION(not in xa transaction yet) HOLDABILITY true
            < Notice that autocommit now is false for connection because it is part of the global transaction
            < Notice that connection's holdability at this point is CLOSE_CURSORS_AT_COMMIT because it is part of the global transaction
            < CONNECTION(in xa transaction) HOLDABILITY false
            < CONNECTION(in xa transaction) HOLDABILITY false
            < Autocommit on Connection inside global transaction has been set correctly to false
            < CONNECTION(non-xa) HOLDABILITY false
            < STATEMENT HOLDABILITY false
            < STATEMENT HOLDABILITY false
            < STATEMENT HOLDABILITY true
            < PREPARED STATEMENT HOLDABILITY true
            < CALLABLE STATEMENT HOLDABILITY true
            < H@1 id 1
            < H@2 id 2
            < H@3 id 3
            < CONNECTION(xa) HOLDABILITY false
            < STATEMENT(this one was created with holdability false, outside the global transaction. Check it's holdability inside global transaction) HOLDABILITY false
            < STATEMENT(this one was created with holdability true, outside the global transaction. Check it's holdability inside global transaction) HOLDABILITY true
            < STATEMENT(this one was created with default holdability inside this global transaction. Check it's holdability) HOLDABILITY false
            < PREPAREDSTATEMENT(this one was created with default holdability inside this global transaction. Check it's holdability) HOLDABILITY false
            < CALLABLESTATEMENT(this one was created with default holdability inside this global transaction. Check it's holdability) HOLDABILITY false
            < X@1 id 1
            < X@2 id 2
            < Expected SQLException No current connection. :
            < Expected SQLException ResultSet not open. Verify that autocommit is OFF.
            < resume XA transaction and keep using rs
            < Check holdability of various jdbc objects after resuming XA transaction
            < CONNECTION(xa) HOLDABILITY false
            < STATEMENT(this one was created with holdability false, outside the global transaction. Check it's holdability inside global transaction) HOLDABILITY false
            < STATEMENT(this one was created with holdability true, outside the global transaction. Check it's holdability inside global transaction) HOLDABILITY true
            < STATEMENT(this one was created with default holdability inside the global transaction when it was first started. Check it's holdability) HOLDABILITY false
            < PREPAREDSTATEMENT(this one was created with default holdability inside the global transaction when it was first started. Check it's holdability) HOLDABILITY false
            < CALLABLESTATEMENT(this one was created with default holdability inside the global transaction when it was first started. Check it's holdability) HOLDABILITY false
            < STATEMENT(this one was created with default holdability after the global transaction was resumed. Check it's holdability) HOLDABILITY false
            < PREPAREDSTATEMENT(this one was created with default holdability after the global transaction was resumed. Check it's holdability) HOLDABILITY false
            < CALLABLESTATEMENT(this one was created with default holdability after the global transaction was resumed. Check it's holdability) HOLDABILITY false
            < Expected SQLException ResultSet not open. Verify that autocommit is OFF.
            < Expected SQLException ResultSet not open. Verify that autocommit is OFF.
            < Set connection to hold
            < CONNECTION(held) HOLDABILITY true
            < CONNECTION(xa) HOLDABILITY false
            < Expected SQLException(setHoldability) Cannot set holdability ResultSet.HOLD_CURSORS_OVER_COMMIT for a global transaction.
            < HOLDABLE Statement in global xact false connection warning ResultSetHoldability restricted to ResultSet.CLOSE_CURSORS_AT_COMMIT for a global transaction.
            < HOLDABLE PreparedStatement in global xact false connection warning ResultSetHoldability restricted to ResultSet.CLOSE_CURSORS_AT_COMMIT for a global transaction.
            < HOLDABLE CallableStatement in global xact false connection warning ResultSetHoldability restricted to ResultSet.CLOSE_CURSORS_AT_COMMIT for a global transaction.
            < CONNECTION(held) HOLDABILITY true
            < PASS XA HOLDABILITY TEST
            < **Test holdability state for: PooledConnection **
            < PASS: Holdability matches expected holdability:HOLD_CURSORS_OVER_COMMIT
            < ** Test autoCommit state for: PooledConnection**
            < PASS: autoCommit reset on getConnection
            < done creating table
            < *** Test isolation level reset on PooledConnection.getConnection()***
            < setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED
            < PASS: No lock timeout occurs for READ_UNCOMMITTED
            < Get a new connection with PooledConnection.getConnection()
            < Isolation level should be reset to READ_COMMITTED
            < PASS: Expected lock timeout for READ_COMMITTED
            < done creating table
            < *** Test isolation level reset on XAConnection.getConnection()***
            < setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED
            < PASS: No lock timeout occurs for READ_UNCOMMITTED
            < Get a new connection with XAConnection.getConnection()
            < Isolation level should be reset to READ_COMMITTED
            < PASS: Expected lock timeout for READ_COMMITTED
            < Checked class declared as: javax.sql.DataSource
            < Completed checkDataSource30
            Test Failed.
          • End: checkDataSource30 jdk1.5.0_04 DerbyNetClient derbynetmats:jdk14 2006-08-15 02:21:22 ***

        Issue Links

          Activity

          Hide
          Mike Matrigali added a comment -

          I've seen multiple developers report running into the testing failure, bumping priority from minor to major.

          Show
          Mike Matrigali added a comment - I've seen multiple developers report running into the testing failure, bumping priority from minor to major.
          Hide
          Rick Hillegas added a comment -

          Moving to 10.2.2.0.

          Show
          Rick Hillegas added a comment - Moving to 10.2.2.0.
          Hide
          Knut Anders Hatlen added a comment -

          Marking the issue as resolved since the hang has not been seen in the nightlies since before DERBY-1817 was fixed. The fix has also been checked into the 10.2 branch.

          Show
          Knut Anders Hatlen added a comment - Marking the issue as resolved since the hang has not been seen in the nightlies since before DERBY-1817 was fixed. The fix has also been checked into the 10.2 branch.
          Hide
          Andrew McIntyre added a comment -

          This issue has been resolved for over a year with no further movement. Closing.

          Show
          Andrew McIntyre added a comment - This issue has been resolved for over a year with no further movement. Closing.

            People

            • Assignee:
              Unassigned
              Reporter:
              Vemund Østgaard
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development