[ 
https://issues.apache.org/jira/browse/OFBIZ-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-5122.
----------------------------------

    Resolution: Fixed

Thanks Jose Manuel,

Oops I see, I missed to apply the patch from OFBIZ-2599, just handled the DBPC 
part, and Philippe did not notice.

OK so it's just a matter of replacing 
PoolableConnectionFactory factory = new PoolableConnectionFactory(xacf, pool, 
null, null, true, true);
by
PoolableManagedConnectionFactory factory = new 
PoolableManagedConnectionFactory(xacf, pool, null, null, true, true);

Done in 
trunk r1431191
R12.04 r1431191
R11.04 r1431195
R10.04 r1431205

We no longer support R09.04, those interested can make the easy change 
themselves

Too bad we did not notice that for 3.5 years. It seems it does not affect 
servers with plenty of memory, or updated often enough. But I recommend to 
upgrade of course...
                
> 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

Reply via email to