Recently our servers have been experiencing high CPU usage. Adobe support suggested that it could be due to extensive logging that causes a bottle neck. One of our logs is the SOAPUI.log found in /jboss/bin. However, we cannot find what processes write to this soapui.log file. Is there a way to simply turn off the logging to this file? Does anyone have experience with soapui.log and what kind of processes would write to it?
Thanks
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
I am assuming you are using JBoss, Did you check the log configuration file? This file is usually named log4j.xml
, logback.xml
, or jboss-log4j.xml
. It can be found in the JBoss configuration directory, often located at <JBOSS_HOME>/standalone/configuration/
or <JBOSS_HOME>/domain/configuration/
.
In the logging configuration file, look for the <appender>
elements. Each appender configuration specifies the target log file or destination. Next, locate the <logger> or <category> elements in the logging configuration. These elements specify the logging level and optionally the appender(s) associated with each logger. Check the configuration of each logger to see which classes or packages it applies to. Loggers are typically named after the classes or packages they handle logging for. For example, a logger named com.example would handle logging for classes in the com.example package and its sub-packages.
Hope this helps.
Hi,
I am assuming you are using JBoss, Did you check the log configuration file? This file is usually named log4j.xml
, logback.xml
, or jboss-log4j.xml
. It can be found in the JBoss configuration directory, often located at <JBOSS_HOME>/standalone/configuration/
or <JBOSS_HOME>/domain/configuration/
.
In the logging configuration file, look for the <appender>
elements. Each appender configuration specifies the target log file or destination. Next, locate the <logger> or <category> elements in the logging configuration. These elements specify the logging level and optionally the appender(s) associated with each logger. Check the configuration of each logger to see which classes or packages it applies to. Loggers are typically named after the classes or packages they handle logging for. For example, a logger named com.example would handle logging for classes in the com.example package and its sub-packages.
Hope this helps.
@Tony30383138k8g3 Did you find the suggestion users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.
Views
Replies
Total Likes
Views
Likes
Replies