Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-17857

CLONE -db connection leak

    Details

    • CLE Team Issue:
      Yes
    • Previous Issue Keys:
      KNL-399

      Description

      We are continuing to see a db connection leak in 2.6. That is, the number of active connections continues rising. I just looked at all calls to borrowConnection in the kernel, and they all have the same bug: they are in a try block, but the borrowConnection is inside the try. That means that if the catch ever triggers, the connection won't be returned. The fix is obvious: move the definition of connection outside the try, and add a finally that returns it.

      It looks like we need to do a global search for borrowConnection and getConnection throughout Sakai. Anyone want to do this?

      I'd really like this to be fixed for 2.7. I'm getting tired of having to restart Sakai due to this problem.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  maintenanceteam Core Team
                  Reporter:
                  hedrick Charles Hedrick
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code