On 3/9/2011 8:50 AM, Rick Hillegas wrote:
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 should have reopened the old one, but didn't see it when I searched the open issues, so logged a new issue. Either way DERBY-5109 should be analyzed as a current issue.o DERBY-5109: This appears to be a duplicate of an already fixed issue.
