Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Message-ID: <16455973.1154290695730.JavaMail.jira@brutus>
Date: Sun, 30 Jul 2006 13:18:15 -0700 (PDT)
From: "Phil Steitz (JIRA)" <jira@apache.org>
To: commons-dev@jakarta.apache.org
Subject: [jira] Reopened: (DBCP-102) [dbcp] setReadOnly & setAutoCommit
 called too many times
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DBCP-102?page=all ]

Phil Steitz reopened DBCP-102:
------------------------------

             
Per last comment, passivateObject should also be fixed.

> [dbcp] setReadOnly & setAutoCommit called too many times
> --------------------------------------------------------
>
>                 Key: DBCP-102
>                 URL: http://issues.apache.org/jira/browse/DBCP-102
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2 Final
>         Environment: Operating System: other
> Platform: Sun
>            Reporter: AC
>             Fix For: 1.2.2
>
>
> 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.

-- 
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org