KS Idea Tracker
  1. KS Idea Tracker
  2. KSLAB-548

KS-Standalone not properly cleaning up db connections, flooding server

    Details

    • Type: Bug/Defect Bug/Defect
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Cannot Reproduce
    • Affects Version/s: R1 M4.1
    • Fix Version/s: None
    • Component/s: Deployment
    • Labels:
      None
    • KS Environment:
      Tomcat/Oracle/Redhat
    • Steps to Reproduce:
      This seems to be most easily repeated when you navigate to Orgs in KS. This has not been seen on embedded installs, just standalone.

      Description

      Oracle XE
      KS Standalone

      Don't think we're cleaning up our db connections properly. Logs get flooded with these messages:

      59034030 [Thread-2] ERROR org.enhydra.jdbc.xapool - GenericPool:cleanUp Error Exception in GenericPool:cleanUp

      And the XE services eventually runs out of threads/processes

      java.sql.SQLException: SQLException in StandardPoolDataSource:getConnection no connection available java.sql.SQLException: Cannot get connection for URL jdbc:oracle:thin:@appserv-2.ks.kuali.net:1521:XE : Listener refused the connection with the following error:
      ORA-12519, TNS:no appropriate service handler found
      The Connection descriptor used by the client was:
      appserv-2.ks.kuali.net:1521:XE

      at org.enhydra.jdbc.pool.StandardPoolDataSource.getConnection(StandardPoolDataSource.java:204)
      at org.enhydra.jdbc.pool.StandardPoolDataSource.getConnection(StandardPoolDataSource.java:164)
      at org.springframework.scheduling.quartz.LocalDataSourceJobStore$2.getConnection(LocalDataSourceJobStore.java:125)
      at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:112)
      at org.quartz.impl.jdbcjobstore.JobStoreCMT.getNonManagedTXConnection(JobStoreCMT.java:164)
      at org.quartz.impl.jdbcjobstore.JobStoreSupport.doCheckin(JobStoreSupport.java:3070)
      at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:3713)
      at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:3749)

      You can see the XE service in state:blocked and the large amount of "established" connections.

      Service "XE" has 1 instance(s).
      Instance "XE", status READY, has 1 handler(s) for this service...
      Handler(s):
      "DEDICATED" established:1343 refused:1 state:blocked
      LOCAL SERVER

        Issue Links

          Activity

          Hide
          Kyle Campos (Inactive) added a comment -

          Issue no longer seen on M4-4 w/Oracle Enterprise.

          Show
          Kyle Campos (Inactive) added a comment - Issue no longer seen on M4-4 w/Oracle Enterprise.
          Hide
          Kyle Campos (Inactive) added a comment -

          I've not been able to reproduce this on fresh oracle instances on EC2. Closing.

          Show
          Kyle Campos (Inactive) added a comment - I've not been able to reproduce this on fresh oracle instances on EC2. Closing.
          Hide
          Kyle Campos (Inactive) added a comment -

          I've not been able to reproduce this on fresh oracle instances on EC2. Closing.

          Show
          Kyle Campos (Inactive) added a comment - I've not been able to reproduce this on fresh oracle instances on EC2. Closing.

            People

            • Assignee:
              Kyle Campos (Inactive)
              Reporter:
              Kyle Campos (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel