You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Amita Vadhavkar (JIRA)" <tu...@ws.apache.org> on 2007/05/21 15:30:21 UTC
[jira] Updated: (TUSCANY-1295) Resolve Memory Leaks in RDB DAS
source and test cases code
[ https://issues.apache.org/jira/browse/TUSCANY-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amita Vadhavkar updated TUSCANY-1295:
-------------------------------------
Attachment: JProfReportsMay21.zip
JIRA1295_952_May21.txt
Below is the analysis. attached are jprofiler reports for each check point.
In summary, 2) will suffice for now to have least changes, but the real
improvement will be by using 3) and 4). Also, need inputs about why the
members are final in 5).
Other than finalize() all other code changes are in UT cases and are marked
with //MM.
As, this JIRA is opened when OutOfMemory was detected during adding
test cases for JIRA-952, the attached patch has changes for JIRA-1295 as well as
JIRA-952. JIRA-952 changes are already reviewed and are marked with //JIRA-952.
0) plain code from trunk
CHECK POINT 0
mvn 7M/12M
jprofiler- FromTrunk_May21
1) add multi schema code, no test cases
CHECK POINT 1
mvn 10M/22M
jprofiler AddedMultiSchema_May21
2) add test cases with small config files
CHECK POINT 2
mvn 10M/23M
jprofiler AddedMultiSchemaUT_May21
3)add finalize()
CHECK POINT 3
mvn 10M/24M
jprofiler AddedFinalize_May21
4)add Connection Pool and separate DasTest and DatabaseSetup
CHECK POINT 4
mvn 6M/14M
jprofiler AddedConnectionPool_May21
5) As Config seems to be the culprit, some more considerations:-
DeleteCommandImpl, DatabaseObject, ResultMetaData - why ConfigWrapper is made final?
HeapWalker shows improvement after 3) and 4)
Also, comparing 3) with 4) , mvn results shows drastic improvement.
> Resolve Memory Leaks in RDB DAS source and test cases code
> ----------------------------------------------------------
>
> Key: TUSCANY-1295
> URL: https://issues.apache.org/jira/browse/TUSCANY-1295
> Project: Tuscany
> Issue Type: Bug
> Components: Java DAS RDB
> Affects Versions: Java-DAS-M3
> Reporter: Amita Vadhavkar
> Attachments: JIRA1295_952_May21.txt, JProfReportsMay21.zip
>
>
> It is seen that as the number of test cases in RDB DAS JUnit testing increase, the memory consumption increase
> and beyond a certail limit, there is OutOfMemory exception for heap memory. This JIRA is created to elaborate the
> cause-solution for this and provide the fix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org