It is all commons-logging with log4j2, so did you try editing WEB-INF/classes/l og4j2.xml and setting it up so it doesn't log to the console?
You are not the first person to bring this up, so if you divide on a sane config let us know and I will commit it. On Thu, Jul 11, 2024 at 2:08 AM Amit Patil <amitpatil12.a...@gmail.com> wrote: > Hello, > Does someone know about the DEBUG_FRAME messages in catalina.out after > starting the services? We have java web services which are started via > tomcat. And use axis2-1.8.2 with tomcat. After starting the tomcat, the log > file gets flooded with DEBUG_FRAME messages in it and if we see the stack > trace, these DEBUG_FRAME log lines seem to come from > org.apache.axis2.util.JavaUtils.callStackToString > Below are the logs. > [2023-09-08T10:02:34,006]DEBUG[main] - DEBUG_FRAME = > org.apache.axis2.util.JavaUtils.callStackToString(JavaUtils.java:564) > DEBUG_FRAME = > org.apache.axis2.description.AxisService.mapActionToOperation(AxisService.java:878) > DEBUG_FRAME = > org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:378) > DEBUG_FRAME = > org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101) > DEBUG_FRAME = > org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:117) > DEBUG_FRAME = > org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:232) > > Can someone please explain how to avoid these logs flooding into > catalina.out? > > Kind Regards, > Amit Patil > >
