[
https://issues.apache.org/jira/browse/METAMODEL-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kasper Sørensen resolved METAMODEL-36.
--------------------------------------
Resolution: Fixed
This was implicitly fixed by adding the pool concept in METAMODEL-39
> Avoid always holding a JDBC connection for every JdbcCompiledQuery
> ------------------------------------------------------------------
>
> Key: METAMODEL-36
> URL: https://issues.apache.org/jira/browse/METAMODEL-36
> Project: Metamodel
> Issue Type: Improvement
> Affects Versions: 4.0
> Reporter: Kasper Sørensen
> Assignee: Kasper Sørensen
>
> We have a issue that a JdbcCompiledQuery always holds a connection and reuses
> this connection whenever the compiled query gets fired. This isn't quite
> elastic enough and also makes for a resource leak if a lot of compiled
> queries are created. Rather we should have the connections acquired grow and
> shrink as per the usage of the query.
> This issue has already been resolved in the eobjects.org codebase.
> See http://eobjects.org/trac/ticket/1206
--
This message was sent by Atlassian JIRA
(v6.2#6252)
