Øystein Grøvlen (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-230?page=all ]Øystein Grøvlen updated DERBY-230: ---------------------------------- Attachment: derby-230c.diff Attaching a new version of the patch since the test with 200 threads once in a while experienced locking timeouts. Hence, I am going back to 100 threads. Also removed some unintentional property settings.
Thanks for your patience with this patch, Øystein. I applied the latest patch to a clean codeline and ran your new test successfully with all three frameworks: embedded, DerbyNet, and DerbyNetClient.
While your new test isn't 100% reliable in detecting a 'regression' of this issue, I nonetheless think that's acceptable since, in the event that a regression _does_ happen, odds are good that 1) it'll show up in your new test within a couple of days, and 2) most people won't be affected.
Unless someone objects (if you do, say so now!), I vote +1. Could a committer please commit?
Thanks, Army
