On Sun, 2011-06-19 at 15:10 -0400, feedly team wrote: > any ideas where to go from here? I am not sure how to debug this further. >
Each HTTP connection should carry a unique ID (a simple integer count). You can see in the log when a particular connection gets leased from the pool and whether it ever gets released back. This should give you enough information to find out where your code leaks connections. Oleg > On Fri, Jun 3, 2011 at 1:10 AM, feedly team <[email protected]> wrote: > > > After turning on logging, the total issued in this message keeps growing > > and growing: > > > > org.apache.http.impl.conn.tsccm.ConnPoolByRoute.getEntryBlocking[FINE|feed-processor-16|21:46:47]: > > [HttpRoute[{}->http://img.ffffound.com]] total kept alive: 240, total > > issued: *160*, total allocated: 400 out of 400 > > > > Today it started at 100 and is now 160. the day before it started at 30 and > > ended at 100. > > > > There is actually one more method I use httpclient within, it is a little > > more complex but still very similar to my other code in its usage of > > httpclient. It is below. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
