You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Kyohei Nakamura (JIRA)" <ji...@apache.org> on 2016/03/15 06:54:33 UTC
[jira] [Updated] (DBCP-455) Even if the cacheState is false, the
getAutoCommit and isReadOnly method always return cached value
[ https://issues.apache.org/jira/browse/DBCP-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kyohei Nakamura updated DBCP-455:
---------------------------------
Attachment: PoolableManagedConnectionFactory.java.patch
PoolableConnectionFactory.java.patch
patchs
> Even if the cacheState is false, the getAutoCommit and isReadOnly method always return cached value
> ---------------------------------------------------------------------------------------------------
>
> Key: DBCP-455
> URL: https://issues.apache.org/jira/browse/DBCP-455
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 2.1.1
> Reporter: Kyohei Nakamura
> Priority: Minor
> Attachments: PoolableConnectionFactory.java.patch, PoolableManagedConnectionFactory.java.patch
>
>
> Even if the cacheState is false, the getAutoCommit and isReadOnly method always return cached value when the poolPreparedStatements is false.
> In my analytics, the cacheState is set to the PoolingConnection but is not set to the PoolableConnetcion.
> Therefore, the PoolableConnetcion always enable caching.
> The PoolableConnetcion should be set the cacheState.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)