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
- is related to
-
-
- Closed
-
- Trackbacks
-
![[Confluence: KC Kuali Coeus (Research Administration)]](/images/icons/generic_link_16.png "[Confluence: KC Kuali Coeus (Research Administration)]")
KC Tech Leads Meeting - 1-16-2013
Venue: Google hangout Attendees: Agenda # Discuss MySQL release script issues. # IaSt. collab issue ## upgraded KRice to 2.1.2 ## then upgraded KC to 5.0.1 ## at issue is our KC3.0>5.0.1 scripts rely on older (preKR2.1....
-
Kuali Technical Integration - January 23, 2013
Date and Time: Every Wednesday, 12:001:00pm ET / 11:0012:00pm CT / 9:0010:00am PT Location: Video Bridge 220488, Dial 8128567060 to connect via phone (conference number 220488#,...
Activity
Modified as discussed, ensured compiler used all debug info, tagged 1.5.0-patch4 https://svn.kuali.org/repos/foundation/legacy/xapool-1.5.0/tags/ and deployed http://shrub.appspot.com/maven.kuali.org/external/xapool/xapool/1.5.0-patch4/ we should be good pending the KTI's approval.
Eric W has seen this happen. If the DB goes down an infinite loop occurs in the cleanup.
updated xapool 1.5.0-patch3 to 1.5.0-patch4
The error is getting logged from http://svn.kuali.org/repos/foundation/legacy/xapool-1.5.0/trunk/src/org/enhydra/jdbc/pool/GenericPool.java search on GenericPool:cleanUp Error Exception in GenericPool:cleanUp
We could change that error to info, there are 4 other log.errors so setting the level to FATAL can miss the others. Peter noted that we could also at least add the exception message to the log.