[
https://issues.apache.org/jira/browse/OFBIZ-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-9385:
-----------------------------------
Description:
I found several cases. This is an improvement only because no cases were
reported. But obviously in case of unlucky exception after the
EntityListIterator creation and before it's closed the EntityListIterator
remains in memory. It should be closed in EntityListIterator.finalize() but the
less happens there the better.
The solution is to use try-with-ressources when (easily) possible (some cases
are quite convoluted)
was:I found several cases. This is an improvement only because no cases were
reported. But obviously in case of unlucky exception after the
EntityListIterator creation and before it's closed the EntityListIterator
remains in memory. It should be closed in EntityListIterator.finalize() but the
less happens there the better.
> EntityListIterator closed but not in case of exception
> ------------------------------------------------------
>
> Key: OFBIZ-9385
> URL: https://issues.apache.org/jira/browse/OFBIZ-9385
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Jacques Le Roux
> Priority: Minor
> Fix For: Upcoming Release
>
>
> I found several cases. This is an improvement only because no cases were
> reported. But obviously in case of unlucky exception after the
> EntityListIterator creation and before it's closed the EntityListIterator
> remains in memory. It should be closed in EntityListIterator.finalize() but
> the less happens there the better.
> The solution is to use try-with-ressources when (easily) possible (some cases
> are quite convoluted)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
