Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Application Requirement:
      KC
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      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
      

        Attachments

          Issue Links

            Activity

            gathreya Gayathri Athreya created issue -
            gathreya Gayathri Athreya made changes -
            Field Original Value New Value
            Description {code}
            >> 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
            {code}
            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 looging 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.
            {code}
            >> 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
            {code}
            gathreya Gayathri Athreya made changes -
            Link This issue is relied upon by KSLAB-548 [ KSLAB-548 ]
            gathreya Gayathri Athreya made changes -
            Link This issue is relied upon by KSLAB-548 [ KSLAB-548 ]
            gathreya Gayathri Athreya made changes -
            Link This issue is related to KSLAB-548 [ KSLAB-548 ]
            gathreya Gayathri Athreya made changes -
            Description 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 looging 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.
            {code}
            >> 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
            {code}
            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.
            {code}
            >> 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
            {code}
            eghm-kuali-m Erik Meade made changes -
            Assignee Erik Meade [ eghm-kuali-m ]
            eghm-kuali-m Erik Meade made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            gathreya Gayathri Athreya made changes -
            Link This issue cloned to KULRICE-8855 [ KULRICE-8855 ]
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            spatterson Shem Patterson (Inactive) made changes -
            Workflow custom [ 162446 ] Copy of custom for rice [ 215397 ]
            spatterson Shem Patterson (Inactive) made changes -
            Workflow Copy of custom for rice [ 215397 ] custom [ 225145 ]
            spatterson Shem Patterson (Inactive) made changes -
            Workflow custom [ 225145 ] Rice Workflow [ 234893 ]

              People

              • Assignee:
                eghm-kuali-m Erik Meade
                Reporter:
                gathreya Gayathri Athreya
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: