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

Change default pooling for Sakai 11

    XMLWordPrintable

    Details

    • Type: Task
    • Status: RESOLVED
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 11.0
    • Fix Version/s: 11.0
    • Component/s: Kernel
    • Labels:
      None

      Description

      Now that we will no longer be supporting HSQLDB, I believe that the work for KNL-1000 and the tomcat pooler should be switched over at the default for Sakai 11.

      I spent some time tonight just trying to figure out why DBCP jars were conflicting, and it looks like this has come up with other people. [1] Switching over to this pooler solved all my problems. And this pooler is supposed to have a lot of advantages over the dbcp one. [2] At least switch this over in trunk and see how it goes. It's possible to switch it back and forth via a configuration file [3]

      [1] http://collab.sakaiproject.org/pipermail/sakai-dev/2013-May/022651.html

      [2] http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html#Introduction

      [3] https://confluence.sakaiproject.org/display/REL/More+Flexible+Sakai+Configuration

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jonespm Matthew Jones
                  Reporter:
                  jonespm Matthew Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code