Derby
  1. Derby
  2. DERBY-5 Network Server Protocol error when select fails and "order by" is specified
  3. DERBY-529

Data cleanup when exception is caught in Network Server may not be complete; need follow-up investigation.

    Details

    • Type: Sub-task Sub-task
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.0.2.1, 10.1.1.0, 10.2.1.6
    • Fix Version/s: None
    • Component/s: Network Server
    • Labels:
      None

      Description

      The patch that was submitted for DERBY-5 (svn revision 56215) solved the specific problem described in that issue but, as indicated by the comments in DERBY-5, it did not take into account cases where the buffer that we're trying to "clear" (because of error) has already been transmitted to the client, thus making it impossible to "undo" the write. It'd be good to look at this particular situation more to figure out 1) if it is actually possible (and if so, can we get a repro?), and 2) if so, how do we fix it?

      I'm filing this as a sub-task so that we can track it separately from DERBY-5 (the specific issue described in DERBY-5 was correctly fixed by svn 56215 and thus should be closed).

        Activity

        A B created issue -
        Gavin made changes -
        Field Original Value New Value
        Workflow jira [ 12323676 ] Default workflow, editable Closed status [ 12797613 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            A B
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development