Original address: Https://docs.jboss.org/author/display/AS71/Logging+Configuration
Overview
The overall server logging configuration is represented by the logging subsystem. It consists of three notable parts: handler configurations, logger and the root logger Declarat Ions (aka Log categories). Each logger does reference a handler (or set of handlers). Each handler declares the log format and output:
<subsystem xmlns=
"urn:jboss:domain:logging:1.0"
>
<console-handler name=
"CONSOLE" autoflush=
"true"
>
<level name=
"DEBUG"
/>
<formatter>
<pattern-formatter pattern=
"%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"
/>
</formatter>
</console-handler>
<periodic-rotating-file-handler name=
"FILE" autoflush=
"true"
>
<formatter>
<pattern-formatter pattern=
"%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"
/>
</formatter>
<file relative-to=
"jboss.server.log.dir" path=
"server.log"
/>
<suffix value=
".yyyy-MM-dd"
/>
</periodic-rotating-file-handler>
<logger category=
"com.arjuna"
>
<level name=
"WARN"
/>
</logger>
[...]
<root-logger>
<level name=
"DEBUG"
/>
"CONSOLE"
/>
"FILE"
/>
</root-logger>
</subsystem>
|
Why is there alogging.propertiesFile?
You are noticed that there is a logging.properties file in the configuration directory. This logging configuration was used when the server boots up until the logging subsystem kicks in. If The logging subsystem is not a included in your configuration and then this would act as the logging configuration for the E Ntire server.
In the "This" may go away or be automatically generated from the logging subsystem. For most users the this file is should not being modified.
Note: If the logging.properties is not available during start there would be no logging until the logging subsystems kicks in, th Is are also the case if the configuration is damaged, the server might exit without any further message.
Default Log File locationsmanaged Domain
In a managed domain, types of log files do Exist:controller and server logs. The controller components govern the domain as whole. It ' s their responsibility to Start/stop server instances and execute managed operations throughout the domain. Server logs contain the logging information for a particular server instance. They was co-located with the host the server was running on.
For the sake of simplicity we are at the default setup for managed domain. In this case, both the domain controller and the servers is located on the same host:
Process |
Log File |
Host Controller |
./domain/log/host-controller/boot.log |
Process Controller |
./domain/log/process-controller/boot.log |
"Server One" |
./domain/servers/server-one/log/boot.log |
"Server One" |
./domain/servers/server-one/log/server.log |
"Server three" |
./domain/servers/server-three/log/boot.log |
"Server three" |
./domain/servers/server-three/log/server.log |
|
The server logs as know it from previous JBoss as versions is located in the servers subdirectory:i.e. ./domain/servers/server-three/log/server.log |
Standalone Server
The default log files for a standalone server can be found in the log subdirectory of the distribution:
Process |
Log File |
Server |
./standalone/log/boot.log |
Server |
./standalone/log/server.log |
JBoss 7 AS1 Log Configuration