0

The console logging file increases without limiting the overall size. In some cases, it fills the entire file system. The file size needs to be capped with a limit and start rolling out the old logs and keep only newer ones like any other application log files.

The following is standalone.xml configuration

<console-handler name="CONSOLE" >
                <level name="INFO"/>
                <formatter>
                    <named-formatter name="COLOR-PATTERN"/>
                </formatter>
            </console-handler>

The following is logging.properties configuration

logger.handlers=FILE,CONSOLE
handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler
handler.CONSOLE.level=INFO
handler.CONSOLE.formatter=COLOR-PATTERN
handler.CONSOLE.properties=enabled,autoFlush,target
handler.CONSOLE.enabled=true
handler.CONSOLE.autoFlush=true
handler.CONSOLE.target=SYSTEM_OUT

The following is the start-up configuration

if [ -z "$JBOSS_CONSOLE_LOG" ]; then
        JBOSS_CONSOLE_LOG=/log/AppServer/console.log
fi

Tried handling the console.log file using file handlers.

Piotr P. Karwasz
  • 12,857
  • 3
  • 20
  • 43
Jyoti
  • 1
  • Where is that "start-up configuration" located? I assume that pipes stdout to a file which you can't tell WildFly how to rotate as it thinks it's just writing to `System.out`. – James R. Perkins Feb 02 '23 at 16:10

0 Answers0