Hi, We have an application which has more than 100, 000 logs per second. We want to make sure all logs will be kept. So we use DefaultAsyncQueueFullPolicy.
The problem we have is that a log will be compressed when reaching 5GB. Before the log finishes compression, a new log will reach 5GB and also needs to be compressed. Then log method will be stuck, causing the application stuck. Is it a limitation of log4j? Is there anything I can do to solve this problem? Maybe with some configurations? Best Regards, Chenxi Li
