On 3/7/06, John Embretsen <[EMAIL PROTECTED]> wrote: > Deepa Remesh wrote: > > > Thanks John for uploading your repro. I have not been able to look at > > it closely as jira seems to be having problems again. I was wondering > > if you have the results from your DOTS test. Please post if you have > > any updates. > > Actually, the DOTS test failed, i.e. the network server hit an > OutOfMemoryError (PermGenSpace) after about 56 hours (not much longer than > without the patch), but I suspect that something is not right... >
Thanks for the update. Here is how I interpreted the test results from John's mails and comments at https://issues.apache.org/jira/browse/DERBY-210#action_12364800 http://www.nabble.com/Re%3A-jira-Updated%3A-%28DERBY-210%29-Network-Server-will-leak-prepared-statements-if-not-explicitly-closed-by-the-user-until-the-connection-is-closed-p2783155.html http://www.nabble.com/Re%3A-jira-Updated%3A-%28DERBY-210%29-Network-Server-will-leak-prepared-statements-if-not-explicitly-closed-by-the-user-until-the-connection-is-closed-p3279845.html * Without any patches, DOTS test gives first OOME after 3 hours. * With my first draft patch, DOTS test ran upto 55 hours before giving an OOME. * With patch5, DOTS test ran upto 56 hours before giving an OOME. If the above statements are correct, I think patch5 is improving the memory usage. It solves the specific problem of memory leak of prepared statements. It looks like Derby client driver still has some more areas which can be possibly improved. If this is the case, I think it would be good to get patch5 committed and we can open new JIRA issues to track the remaining OOMEs. Thanks, Deepa
