ramanathan1504 commented on issue #4356:
URL: 
https://github.com/apache/logging-log4j2/issues/4356#issuecomment-6007098732

   @plusterkopp 
   
   Thanks for testing it in your server. Good to hear no events are discarded.  
                                                                                
                 
                                                                                
                                                                                
                   
   The idle `RollingFileManager` threads are not from this fix. They come from 
#4165 on `2.x`, which made each rolling appender keep one thread after its 
first rollover. Do you have about 30 rolling file appenders? If so, that 
explains the count. I will open a separate issue for it.                        
                                            
                                                                                
                                                                                
                          
   No need to try 2.26.2. It does not have this fix yet.                        
                                                                                
                 
                                                                                
                                                                                
                   
   For source jars, add `source:jar-no-fork`:                                   
                                                                                
                 
                                                                                
                                                                                
                   
   `./mvnw source:jar-no-fork install -pl 
:log4j-api-java9,:log4j-core-java9,:log4j-core -am -DskipTests` 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to