https://issues.apache.org/bugzilla/show_bug.cgi?id=47583
Summary: Fix occasional test failure in TestConcurrency
Product: Tomcat 7
Version: trunk
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: Modules: jdbc-pool
AssignedTo: dev@tomcat.apache.org
ReportedBy: s...@apache.org
Created an attachment (id=24039)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=24039)
Sample test run showing failures
TestConcurrency exhibits occasional failures - about 10% in my tests - which
appear to be due to a startup timing issue.
This can be fixed by replacing:
assertEquals("Size comparison:",10, ds.getPool().getSize());
by
assertTrue("Size comparison(less than 11):",ds.getPool().getSize()<=10);
in the testSimple() method (as has been done for the other test methods in the
class).
See attached files for some sample failures.
N.B. the test output indicates either no failures or two failures.
This suggests that the failure in testSimple() may be affecting a subsequent
test, i.e. there may be a problem with the test cleanup.
Perhaps Driver.reset(); should be done after ds.close() - or even after
super.tearDown()?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
