On 05/02/2012 05:26 PM, Jacopo Cappellato wrote: > > On May 2, 2012, at 11:32 PM, Adam Heath wrote: > >> If the root cause *is* a time-slice issue, the fix is to *not* >> increase the timeout. Dead stop. Changing the timeout will just >> cause it to again fail at some point in the future when computers get >> faster yet again. > > I would instead increase the timeout and then revisit the issue when we will > run OFBiz in the computer of the future... but if you are willing to fix this > without this tweak then you are most welcome.
Increasing timeouts to fix a race condition just shows there might actually be a very rare race condition that happen in production cases. Who here likes fixing race conditions that only happen when OOM is occuring? It's not that there is a mem-leak, or that the problem is OOM, but that only when an object is garbage-collected just before OOM is thrown, and other nearby-code doesn't like the object going away, and the race then occurs.
