[DBCP-102] [dbcp] setReadOnly & setAutoCommit called too many times

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 1.2.2

Environment

Operating System: other
Platform: Sun

• Bugzilla Id: 31343
• Assignee: Unassigned
• Reporter: AC
• Created: 21/Sep/04 22:18
• Updated: 16/Feb/09 15:51
• Resolved: 23/Jul/07 19:02

Description

In order to gain some processor time for my application that uses Hibernate, I
looked with optimizeIt where it spends time. It seems that for a request on the
database (Oracle 9) around 25% (!!?) is spent on getting the connection from
the DBCP pool, and this not only the first time!. The methods that provoke this
loss of time are connection.setReadOnly and connection.setAutoCommit called
inside the method PoolableConnectionFactory.activateObject. Looking to the
stack, these calls translate to communication with the Oracle server.
The obvious thing to do is to check if read only and autocommit flags are
already set to the expected values. (Of course, Oracle could 've done this too,
but I hope you'll have a faster response )

Thank you very much for you help.

Issue Links

• is blocked by: DBCP-97 setAutoCommit(true) when returning connection to the pool