Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.1
-
None
-
None
-
Operating System: other
Platform: All
-
25001
Description
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.