[
https://issues.apache.org/jira/browse/OFBIZ-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549510#comment-13549510 ]
Jose Manuel Vivó Arnal commented on OFBIZ-5122:
-----------------------------------------------
Thanks Jacques about the fast solution.
Hello Anil,
This is how we did the stress test to repeat the problem in a few minutes instead days (this take us some time ;-) ):
* set JVM memory settings to: -Xms128M -Xmx155M -XX:MaxPermSize=80m
* Modify entityengine.xml to set time-between-eviction-runs-millis to 500 and pool-min-size to 0
* Modify DBCPConnectionFactory to set pool MaxWait to 1200 and MinEvictableIdleTimeMillis to 500
I can attach a image about memory usage (made with visualVM) before and after patch.
Regards,
Chema
> Memory leak due to transaction management using DBCP and MySQL
> --------------------------------------------------------------
>
> Key: OFBIZ-5122
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5122> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Environment: Linux, MySQL 5.5.28
> Reporter: Jose Manuel Vivó Arnal
> Assignee: Jacques Le Roux
> Priority: Critical
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> After several hours looking for the memory-leak, we found than the problem is the very same that OFBIZ-2599
> This issue has a patch file attached for DBCPConnectionFactory class (patch-DBCPConneectionFactory.txt) which is not applied to specified versions.
> We check that this patch solves the problem.
> Please, apply this patch.
> Thank you in advance.
> --
> Jose Manuel Vivó Arnal
> DiSiD Technologies (
http://www.disid.com)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Locked
