Unless I am reading the output of the latest failures wrong or we are picking up the wrong hashcode (should be innermost delegate), this is now looking like it could be a pool bug - allowing more than maxActive distinct connections to be simultaneously active. Need to look at this some more. It is worth temporarily modifying the pom to use pool 1.4 for a test.
Phil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
