DEBUG_FRAME messages in catalina.out log file
Amit Patil <[email protected]> Thu, 11 Jul 2024 17:37:31 +0530
| Newsgroups | gmane.text.xml.axis.user |
|---|---|
| Message-ID | <CAKHBusMRpLqHjM+0hqy0AE6Fh66Gkj5AGVkeCZ7HQw+7Qq6pCA@mail.gmail.com> |
--00000000000038964c061cf79ca5 Content-Type: text/plain; charset="UTF-8" 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 --00000000000038964c061cf79ca5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hello,<br><div>Does someone know about the DEBUG_FRAME mes= sages in catalina.out after starting the services? We have java web service= s which are started via tomcat. And use axis2-1.8.2 with tomcat. After star= ting 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 fro= m org.apache.axis2.util.JavaUtils.callStackToString<br>Below are the logs.= =C2=A0<br><font size=3D"1" face=3D"monospace">[2023-09-08T10:02:34,006]DEBU= G[main] - DEBUG_FRAME =3D org.apache.axis2.util.JavaUtils.callStackToString= (JavaUtils.java:564)<br> DEBUG_FRAME =3D org.apache.axis2.description.AxisS= ervice.mapActionToOperation(AxisService.java:878)<br> DEBUG_FRAME =3D org.a= pache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:3= 78)<br> DEBUG_FRAME =3D org.apache.axis2.deployment.ServiceGroupBuilder.pop= ulateServiceGroup(ServiceGroupBuilder.java:101)<br> DEBUG_FRAME =3D org.apa= che.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(Archiv= eReader.java:117)<br> DEBUG_FRAME =3D org.apache.axis2.deployment.repositor= y.util.ArchiveReader.processServiceGroup(ArchiveReader.java:232)<br></font>= <br>Can someone please explain how to avoid=C2=A0these logs flooding into c= atalina.out?=C2=A0<br><font size=3D"1" face=3D"monospace"><br></font>Kind R= egards,</div><div>Amit Patil<font size=3D"1" face=3D"monospace"><br><br></f= ont></div></div> --00000000000038964c061cf79ca5--