On 15/06/2023 11:26, Thomson Waghmare wrote:
I am facing an issue in Linux server that webserver service is restarting
automatically frequently. I tried to enable debug logs by changing the all
logging properties in tomcat-8.5.79/conf/logging.proprties. But I see only
INFO logs but no FINE or FINER or FINEST logs.
For Tomcat:
DEBUG = FINE
TRACE = FINEST
You shouldn't need to change the handler configurations.
Changing these only impact the container (web application) loggers.
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level =
FINEST
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].level
= FINEST
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].level
= FINEST
If you want to impact debug logging for Tomcat's internals try something
like:
org.apache.catalina.core.level=ALL
Be careful. Debug logging tends to impact performance.
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fe638000368, pid=54728,
tid=0x00007fe625309700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_333-b31)
(build 1.8.0_333-b31)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.333-b31 mixed
mode linux-amd64 compressed oops)
# Problematic frame:
# C 0x00007fe638000368
#
# Failed to write core dump. Core dumps have been disabled. To
enable core dumping, try "ulimit -c unlimited" before starting Java
again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid54728.log
Debug logging probably isn't going to help debugging this issue. You
want to look at that log file for the details.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
