On 3/9/11 1:08 PM, Kathey Marsden wrote:
On 3/9/2011 8:50 AM, Rick Hillegas wrote:
o DERBY-5109: This appears to be a duplicate of an already fixed issue.
Except it is not fixed afterall or perhaps what was fixed was another
issue that caused the same symptom.
It just showed up in recent run
On 3/9/2011 8:50 AM, Rick Hillegas wrote:
o DERBY-5109: This appears to be a duplicate of an already fixed issue.
Except it is not fixed afterall or perhaps what was fixed was another
issue that caused the same symptom.
It just showed up in recent run after the fix for DERBY-5074 .
Perhaps,
I see the following open bugs related to the improved handling of
interrupts in Derby. Are there others?
First, there are a couple cleanup bugs which Dag logged. These have to
do with handling error conditions more gracefully. Neither of these
corrupts data or returns wrong results. Neither of
