Database connection is not closed and transaction isn't ended

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Highest
    • 1.4
    • Affects Version/s: 1.3.4
    • Component/s: None
    • Environment:

      Oracle 10g
      Tomcat 5

      Our Confluence production environment has crashed many times during the last few days because some transaction is never ended and the database connection isn't closed. The transaction has obtained locks to content and therefore blocks all updates to certain rows. This causes connection pool to be exhausted and Confluence is no more able to service any users.

      Checking from the database, there is an open connection with event "SQL*Net message from client" meaning that it waits for the client. The connection has obtained locks to content and other tables as well. The connection is established from the Confluence server for sure and has been idle/waiting for hours.

        1. abandonenConnections.txt
          58 kB
          Jarno Peltoniemi
        2. thread-dump.txt
          81 kB
          Jarno Peltoniemi

            Assignee:
            Unassigned
            Reporter:
            Jarno Peltoniemi
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: