[ http://issues.apache.org/jira/browse/OJB-97?page=all ]
Armin Waibel resolved OJB-97:
-----------------------------
Fix Version: 1.0.5
Resolution: Fixed
To solve this issue we have to extend DBCP's PoolableConnectionFactory class
and override some methods, because this class always call Connection.rollback
on connections returned to pool with autoCommit 'false'.
> ConnectionFactoryDBCPImpl: Rollback call after commit call when set
> useAutoCommit="2"
> -------------------------------------------------------------------------------------
>
> Key: OJB-97
> URL: http://issues.apache.org/jira/browse/OJB-97
> Project: OJB
> Type: Bug
> Versions: 1.0.4
> Reporter: Armin Waibel
> Assignee: Armin Waibel
> Fix For: 1.0.5
>
> In method
> org.apache.commons.dbcp.PoolableConnectionFactory#passivateObject(Object obj)
> two undesireable calls are done:
> 1. setAutocommit(true) is always called
> 2. This check: !conn.getAutoCommit() && !conn.isReadOnly() always rollback
> the connection
> The only idea I have is to extend PoolableConnection and override the
> critical methods
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
