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

        Hide
        A B added a comment -

        Unfortunately (or maybe fortunately? , I was never able to come up with a concrete scenario. As the notes in the bug say, one would need 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?". So I wasn't aware of any definite scenarios where this could happen when I filed the issue, and I haven't come across any since then. This was just a potential hole that I noticed when I made the fix for DERBY-5, so I thought it'd be good to file it for tracking purposes.

        I wish I could give you something more specific, but right now this is definitely more abstract than anything. I can see where the problem could theoretically occur, but I do not have any actual examples...

        Show
        A B added a comment - Unfortunately (or maybe fortunately? , I was never able to come up with a concrete scenario. As the notes in the bug say, one would need 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?". So I wasn't aware of any definite scenarios where this could happen when I filed the issue, and I haven't come across any since then. This was just a potential hole that I noticed when I made the fix for DERBY-5 , so I thought it'd be good to file it for tracking purposes. I wish I could give you something more specific, but right now this is definitely more abstract than anything. I can see where the problem could theoretically occur, but I do not have any actual examples...
        Hide
        Bryan Pendleton added a comment -

        Army, do you know of a definite scenario which causes this problem? I've read through the comments in DERBY-5, and I've looked at a few simple cases, but so far I haven't found a case where the buffer that we want to clear has already been transmitted to the client.

        If you don't have a specific scenario in mind, I'll keep looking at this in the abstract, but if you do have something specific, it would be very useful to get a few more details about it.

        thanks,

        bryan

        Show
        Bryan Pendleton added a comment - Army, do you know of a definite scenario which causes this problem? I've read through the comments in DERBY-5 , and I've looked at a few simple cases, but so far I haven't found a case where the buffer that we want to clear has already been transmitted to the client. If you don't have a specific scenario in mind, I'll keep looking at this in the abstract, but if you do have something specific, it would be very useful to get a few more details about it. thanks, bryan

          People

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

            Dates

            • Created:
              Updated:

              Development