You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to set up a clustered-object-pool with no expiration policy to maintain a pool of reusable TCP connections. I use .defaultExpirationPolicy(null) to use NeverExpirePolicy, but the deallocator thread keeps logging these over and over:
[pool-1-thread-2] INFO org.bbottema.genericobjectpool.GenericObjectPool - ExpirationPolicy set to NeverExpire, Skipping invalidation of expired objects!
[pool-1-thread-2] INFO org.bbottema.genericobjectpool.GenericObjectPool - ExpirationPolicy set to NeverExpire, Skipping invalidation of expired objects!
[pool-1-thread-2] INFO org.bbottema.genericobjectpool.GenericObjectPool - ExpirationPolicy set to NeverExpire, Skipping invalidation of expired objects!
[pool-1-thread-2] INFO org.bbottema.genericobjectpool.GenericObjectPool - ExpirationPolicy set to NeverExpire, Skipping invalidation of expired objects!
Maybe this could be logged only once, or using the TRACE level?
As a workaround, I'm using .defaultExpirationPolicy(obj -> false) which does the same thing as NeverExpirePolicy, but the deallocator still has to check objects one by one.
The text was updated successfully, but these errors were encountered:
Hi,
I'm trying to set up a clustered-object-pool with no expiration policy to maintain a pool of reusable TCP connections. I use
.defaultExpirationPolicy(null)
to useNeverExpirePolicy
, but the deallocator thread keeps logging these over and over:Maybe this could be logged only once, or using the TRACE level?
As a workaround, I'm using
.defaultExpirationPolicy(obj -> false)
which does the same thing asNeverExpirePolicy
, but the deallocator still has to check objects one by one.The text was updated successfully, but these errors were encountered: