[KULRICE-8775] xapool cleanup errors Created: 16/Jan/13  Updated: 21/Mar/13  Resolved: 25/Jan/13

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.1.3
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Major
Reporter: Gayathri Athreya Assignee: Erik Meade
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
Relate
is related to KSLAB-548 KS-Standalone not properly cleaning u... Closed
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


 Comments   
Comment by Erik Meade [ 16/Jan/13 ]

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.

Comment by Erik Meade [ 16/Jan/13 ]

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.

Comment by Gayathri Athreya [ 16/Jan/13 ]

Hey, any idea why these are showing up?

Comment by Erik Meade [ 23/Jan/13 ]

Eric W has seen this happen. If the DB goes down an infinite loop occurs in the cleanup.

Comment by Erik Meade [ 25/Jan/13 ]

updated xapool 1.5.0-patch3 to 1.5.0-patch4

Generated at Tue Sep 22 06:39:28 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.