• Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-12958xapool cleanup
      KULRICE-1909Roll back from Atomikos to JOTM/XAPool
      KULRICE-6022XAPool/Bitronix configuration documentation
      KULRICE-877Try replacing JOTM/XAPool with Atomikos
      KULRICE-1811Code cleanup
      KULRICE-6608Misc. KRMS Code cleanup
      KULRICE-4045Look into use of DBCP BasicManagedDataSource to replace XAPool
      KULRICE-2396Please update xapool jar in rice's maven repository
      KULRICE-10052Cleanup parseExpression method
      KULRICE-384Rice Tag Cleanup
    • Application Requirement:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      In KC we see tons of xapool messages filling up the logs, we notice these messages in the Rice logs also. Our guess is that xapool is trying to clean up already closed connections. We have currently set the logging level to fatal to prevent these from filling the logs but that is definitely not the right solution. I do not see a Rice fix version 2.1.4 so added this to 2.1.3. Please move it to 2.1.4 since 2.1.3 is going to freeze soon.

      >> 2013-01-10 20:33:45,348 [Thread-10] u:/d: ERROR org.enhydra.jdbc.xapool - GenericPool:cleanUp Error Exception in GenericPool:cleanUp
      >> 2013-01-10 20:33:45,349 [Thread-16] u:/d: ERROR org.enhydra.jdbc.xapool - GenericPool:cleanUp Error Exception in GenericPool:cleanUp

        Issue Links


          No work has yet been logged on this issue.


            • Assignee:
              Erik Meade
              Gayathri Athreya
            • Votes:
              0 Vote for this issue
              6 Start watching this issue


              • Created:

                Structure Helper Panel