-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Phil,
On 8/1/15 11:12 AM, Phil Steitz wrote: > Sorry the docs are not that clear. The problem is that the config > properties work together to determine behavior and documenting > them individually makes it hard to put the whole picture together. > Improvement patches most welcome :) In any case, here is how it > works: > > Connections are evaluated for abandonment when they are out in > circulation - checked out to clients. If you have set > timeBetweenEvictionRunsMillis to a positive value, pool > maintenance runs every timeBetweenEvictionRunsMillis milliseconds. > If you have removeAbandonedOnMaintenance set to true, each time > maintenance runs the pool removes abandoned connections. If you > have removeAbandonedOnBorrow set to true, the pool removes > abandoned connections if it is nearing depletion when a borrow > request arrives. In both cases, the pool looks at the statistics > that it maintains on the list of all objects checked out by clients > to determine which ones appear to be abandoned. To appear > abandoned means to be checked out by a client but not used for > longer than the removeAbandonedTimeout. For DBCP, "used" means the > connection has been used. So when during all that does the abandoned connection get "logged"? If I have a pool with two connections in it, and the first one gets leaked (after, lets say, 10 seconds) but the second one is returned properly, and the application continues to borrow and return the second connection, what happens? Are you only checking connections for "abandonment" after they are returned and then when a client attempts to borrow that specific connection? Or, are all currently-borrowed connections checked for abandonment whenever any borrow operation is requested? Thanks, - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVvW7pAAoJEBzwKT+lPKRYY0UQAIBXTrkBRNC9j7KBYw8DZFcJ UY+U1WrHi7osxEseupCjSjP/xmmOHoC16LkEXqtil5k8rd5yQ9D5I1imPKYZSjiE GBBkkjrbvlwDq/sRp3fxN8La6ueTed4yyh96J5DFfx0opcTtX06YMnpkJDTN2iTt R3GUKbBo4dNZKIFNGhicR4j9JbSwerxbfJDVpEtb0igO7fQu1dRTDQh7gijyUsZ7 PPa0owq9WOBl5dr4ebsoipirArbLbB4WZqCtteOj5QpafEOYyGuKAjFs6PhodVAR A2BlikA9+s6AUcKVnqP+CabZFNYO/1raZWl61q7vSWNR9YMrSSI6TapCsBgzNDQW p8KloJYqjaZFNGtVW23eDtRjTehABnQqoXrB4OL2CEFqgZVjnfpCDl1K0b8wc01y QNnA0eo40462XkwsRSyMOwtunLu02mGayOrzrn7blJ0f2Kj594+/U6HKqAttRlOX 0Sr2VnYJTaBRACHVjycKjjQh1A1lIIfRoIQ0enMBiw8kZ4rVpQsCvwk/5h54/oap 5osEzulFO7zwqhAxWaHigFG9hCeHJHGr7eT4XUXfUqw+/zg6vI//r5rLExIwSi4D p/R214PYSkEMiz+i4uSu+sUOYpOJbaAnJH0R6kXSKkoDmaaylTyLuHujPvLKPF6b ZV739LJI+k5cgcDEWmjv =PKZ/ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
