[Enhancement] reduce log spam from the batch-module
InteractiveNinja opened this issue · 3 comments
Hello 👋
Firstly, thanks for maintaining this library.
I noticed that when I upgraded to >=v8.11.1, the logs are getting flooded with messages when I run the backend server locally.
I found out that the log statement is from bbottema/generic-object-pool#8, which is used in #529.
15:44:01.147 [pool-1-thread-2|org.bbottema.genericobjectpool.GenericObjectPool] DEBUG - 0 objects invalidated as per expiration policy!
15:44:01.157 [pool-1-thread-2|org.bbottema.genericobjectpool.GenericObjectPool] DEBUG - 0 objects invalidated as per expiration policy!
15:44:01.167 [pool-1-thread-2|org.bbottema.genericobjectpool.GenericObjectPool] DEBUG - 0 objects invalidated as per expiration policy!
15:44:01.177 [pool-1-thread-2|org.bbottema.genericobjectpool.GenericObjectPool] DEBUG - 0 objects invalidated as per expiration policy!
15:44:01.188 [pool-1-thread-2|org.bbottema.genericobjectpool.GenericObjectPool] DEBUG - 0 objects invalidated as per expiration policy!
15:44:01.198 [pool-1-thread-2|org.bbottema.genericobjectpool.GenericObjectPool] DEBUG - 0 objects invalidated as per expiration policy!
I don't think there's anything I need to change to stop the log statements without removing the logging for this library in my project.
I appreciate your time 👍
Well, I think it's good to tweak it so it only logs if there are actual objects invalidated and also perhaps make it TRACE level. Having said that, wouldn't it make sense for you to set the debug level to INFO for org.bbottema.genericobjectpool?
Released tweak in 8.11.3
Thank you kindly for the fast change 👍