You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2003/11/26 09:08:05 UTC

DO NOT REPLY [Bug 25001] New: - PATCH: Oracle 9i and default isolation settings

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25001>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25001

PATCH: Oracle 9i and default isolation settings

           Summary: PATCH: Oracle 9i and default isolation settings
           Product: Commons
           Version: 1.1 Final
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: ozeigermann@c1-fse.de


When using default isolation levels in ctor of PoolableConnectionFactory method
activateObject first sets readonly, then isolation. The problem is Oracle
expects the setting of the isolation level to be the first in a transaction. The
obvious fix, that worked for me would be to revese order, i.e. 
first set isolation then readonly. I will attach a patch for this.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org