The broker delegates log file handling to Log4j2. The default log4j2.properties uses a RollingFile appender for "artemis.log," and I believe this behavior is controlled by the value of the "append" property which is not set and defaults to true. Of course, it's always possible you're hitting a bug. The Apache Log4j community might be more helpful for this particular problem. Have you asked them about this behavior?
Justin On Wed, May 28, 2025 at 7:30 AM <herbert.helmstr...@systema.com> wrote: > Hello comunity, > > normally on artemis broker start the artemis.log is created if not present > or the output is attached to artemis.log, if the file is there. > On a broker restart after a failure we faced a recreate (overwrite) of the > present artemis.log with artemis 2.41. > Unfortunately we have no idea now, what was the reason for the restart. > Did sombody else observe this and what can be the reason for it? > > Regards > > Herbert > ------------------------------ > > *Herbert Helmstreit* > Senior Software Engineer > > Phone: +49 941 / 7 83 92 36 > herbert.helmstr...@systema.com > > www.systema.com > > [image: LinkedIn] <https://www.linkedin.com/company/systema-gmbh/>[image: > Facebook] <https://de-de.facebook.com/SYSTEMA.automation/>[image: XING] > <https://www.xing.com/pages/systemagmbh> > > SYSTEMA > Systementwicklung Dipl.-Inf. Manfred Austen GmbH > > Manfred-von-Ardenne-Ring 6 | 01099 Dresden > HRB 11256 Amtsgericht Dresden | USt.-ID DE 159 607 786 > Geschäftsführer: Manfred Austen, CEO und Dr. Ulf Martin, COO > > P Please check whether a printout of this e-mail is really necessary. > >
