why log4j gc free logging is not suitable for webapp

Viewed 207

I am currently migrating our web services and web application to use Log4j 2.6 logging. Based on the information provided on the website, web application supports partial garbage free logging and does not support full garbage free logging because of the possibility of memory leak. Can anyone help me to understand how logging works if we set TreadLocal enabled in first case and ThreadLocal disable in the second case.

Also, I would like know in what scenarios partial garbage free logging is better than full garbage free logging.

1 Answers
Related