Uploaded image for project: 'Commons DBCP'
  1. Commons DBCP
  2. DBCP-102

[dbcp] setReadOnly & setAutoCommit called too many times

    XMLWordPrintableJSON

    Details

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

      Operating System: other
      Platform: Sun

    • Bugzilla Id:
      31343

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                acraciun@flashmail.com AC
              • Votes:
                1 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: