[ http://issues.apache.org/jira/browse/DERBY-529?page=comments#action_12360635 ]
A B commented on DERBY-529: --------------------------- 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... > Data cleanup when exception is caught in Network Server may not be complete; > need follow-up investigation. > ---------------------------------------------------------------------------------------------------------- > > Key: DERBY-529 > URL: http://issues.apache.org/jira/browse/DERBY-529 > Project: Derby > Type: Sub-task > Components: Network Server > Versions: 10.1.1.0, 10.0.2.1, 10.2.0.0 > Reporter: A B > Priority: Minor > > 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). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
