[teiid-issues] [JBoss JIRA] Updated: (TEIID-1252) LOB handling strategy issues

[ https://jira.jboss.org/browse/TEIID-1252?page=com.atlassian.jira.plugin.s... ] Steven Hawkins updated TEIID-1252: ---------------------------------- Summary: LOB handling strategy issues (was: LOB handling strategry issues) Description: LOBs returned from sources cause executions to stay alive until the user query has been completed - this is true even if the LOB values are not returned to the user. Whenever an execution is kept alive, it's associated connection is held until the execution is closed - thus source connections may be held out of their pool indefinitely. Currently each source execution will attempt to obtain a new connection from the pool, which with LOB handling will cause potentially many connections even to the same source to be held out of the their pool indefinitely. was: LOBs returned from sources cause executions to stay alive until the user query has been completed - this is true even if the LOB values are not returned to the user. Whenever an execution is kept alive, it's associated connection is held until the execution is closed - thus source connections may be held out of their pool indefinately. Currently each source execution will attempt to obtain a new connection from the pool, which with LOB handling will cause potentially many connections even to the same source to be held out of the their pool indefinitely. Reusing connections per request seems attractive, but is not straightforward to implement (requires going all the was into connectorworkitem). The simplest fix would be to have the ws and file executionfactories indicate that their lobs are usable after close - however that still doesn't address potential issues with JDBC or other sources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira