Derby
  1. Derby
  2. DERBY-4690

Too few arguments when generating AM_RECORD_NOT_FOUND error

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.7.1.1
    • Fix Version/s: 10.7.1.1
    • Component/s: Store
    • Labels:
      None

      Description

      The message for AM_RECORD_NOT_FOUND has three parameters, but all the methods that generate an exception with that message, only use two of them. So the generated message ends up looking like this:

      ERROR XSAM6: Record

      {2}

      on page 7 in container 625 not found.

      whereas it should have looked like this:

      ERROR XSAM6: Record 7 on page 1 in container 625 not found.

      I don't know if these messages ever make it all the way up to the application, since they are typically caught by this code block in TableScanResultSet:

      if (se.getMessageId().equals(SQLState.AM_RECORD_NOT_FOUND))

      { // Somehow the row got deleted between the above // doesCurrentPositionQualify() call and here (one way is if // this scan is read uncommitted isolation level). return null; }

      But they may be logged in derby.log if the log severity level is set appropriately.

        Activity

        Hide
        Mike Matrigali added a comment -

        Committed fix to trunk. Don't think it goes to client, so minor code cleanup issue.

        DERBY-4690 Too few arguments when generating AM_RECORD_NOT_FOUND error

        Fixed up arguments to the AM_RECORD_NOT_FOUND exception, the page number argumen
        t was missing.

        m1_jdk16:133>svn commit
        Sending java/engine/org/apache/derby/impl/store/access/btree/BTreeScan.java
        Sending java/engine/org/apache/derby/impl/store/access/conglomerate/GenericScanController.java
        Transmitting file data ..
        Committed revision 959701.

        Show
        Mike Matrigali added a comment - Committed fix to trunk. Don't think it goes to client, so minor code cleanup issue. DERBY-4690 Too few arguments when generating AM_RECORD_NOT_FOUND error Fixed up arguments to the AM_RECORD_NOT_FOUND exception, the page number argumen t was missing. m1_jdk16:133>svn commit Sending java/engine/org/apache/derby/impl/store/access/btree/BTreeScan.java Sending java/engine/org/apache/derby/impl/store/access/conglomerate/GenericScanController.java Transmitting file data .. Committed revision 959701.

          People

          • Assignee:
            Mike Matrigali
            Reporter:
            Knut Anders Hatlen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development