Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.4, core 1.4.1, core 1.4.2
    • Fix Version/s: core 1.4.3
    • Component/s: jackrabbit-core
    • Labels:
      None

      Description

      This only happens with the bundle DerbyPersistenceManager.

      In DerbyPersistenceManager.close() the embedded derby database is shut down and then super.close() is called. There the ConnectionRecoveryManager is closed, which tries to operate on a connection to the already shut down derby database. The log contains entries like:

      25.03.2008 13:49:29 ERROR [Thread-5] ConnectionRecoveryManager: failed to close connection, reason: No current connection., state/code: 08003/40000 (ConnectionRecoveryManager.java, line 453)

        Issue Links

          Activity

          Hide
          Marcel Reutegger added a comment -

          Moved super.close() above derby 'shutdown' in DerbyPersistenceManager.

          Fixed in revision: 640792

          Show
          Marcel Reutegger added a comment - Moved super.close() above derby 'shutdown' in DerbyPersistenceManager. Fixed in revision: 640792
          Hide
          Marcel Reutegger added a comment -

          This issue was introduced with enhancement described in JCR-940.

          Show
          Marcel Reutegger added a comment - This issue was introduced with enhancement described in JCR-940 .
          Hide
          Jukka Zitting added a comment -

          Merged to the 1.4 branch in revision 650342.

          Show
          Jukka Zitting added a comment - Merged to the 1.4 branch in revision 650342.

            People

            • Assignee:
              Unassigned
              Reporter:
              Marcel Reutegger
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development