Each of my top-level functions was allocating a Hector client connection at the top, and releasing it when returning. The problem arose when a top-level function had to call another top-level function, which led to the same thread allocating two connections. Hector was not releasing one of them even though I was explicitly requesting them to be released. This might have been fixed since then, and like I said, I didn't dig into why it was happening. I just made sure to pass along the connection instances as necessary and the problem went away.
On Wed, Jul 14, 2010 at 11:40 AM, shimi <[email protected]> wrote: > do you mean that you don't release the connection back to fhe pool? > > On 2010 7 14 20:51, "Jorge Barrios" <[email protected]> wrote: > > Thomas, I had a similar problem a few weeks back. I changed my code to make > sure that each thread only creates and uses one Hector connection. It seems > that client sockets are not being released properly, but I didn't have the > time to dig into it. > > Jorge > > > > On Wed, Jul 14, 2010 at 8:28 AM, Peter Schuller < > [email protected]> wrote: > > > > > [snip] > ... > >
