Re: [Proxool-developer] Spurious connections caused by Prototyper's apparently wrong connectionCount
UNMAINTAINED!
Brought to you by:
billhorsman
From: Bill H. <arc...@gm...> - 2005-10-03 09:08:23
|
Hi Hrvoje, On 10/1/05, Hrvoje Niksic <hn...@xe...> wrote: > Note especially these two lines: > > 2005-09-27 01:36:56 WARN [poolname] [HouseKeeper]: #1660 was active for > 144709 milliseconds and has been removed automaticaly. The Thread > responsible was named 'Thread-18'. > [...] > 2005-09-27 01:36:57 DEBUG [poolname] [Thread-18]: 1003445 -000257 > (04/32/00) - #1660 removed because it couldn't be reset. > > The connection #1660 has been removed twice, which means it could have > decremented connectionCount twice as well. > > What do you think? I think you're on to something there. I had a first look at this on the train this morning and I'm starting to get my head round it. I'm trying to reproduce the problem in a unit test at the moment. It's tricky getting the connection reset to fail but I can get round that. - Bill |