On 14/01/2010, Phil Steitz <[email protected]> wrote: > Unless I am reading the output of the latest failures wrong or we > are picking up the wrong hashcode (should be innermost delegate),
It's currently the connection returned by getConnection(). I'll fix that. > 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. OK; I think we should see if there are duplicate hashes first. > > Phil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
