Simple Logging Facade for Java (SLF4J) is a logging facade that provides a unified interface for various logging frameworks, such as log4j, java.util.logging, and Logback. It allows for the decoupling of the application code from the underlying logging framework, making it easier to change the logging framework without modifying the application code. Here is a small tutorial to discuss the advantages of using SLF4J versus direct logging configuration.
JBoss Logging
WildFly provides an highly-configurable logging subsystem that can be used both by WildFly core and by applications. The logging subsystem is based on JBoss LogManager project which supports several logging frameworks that you can configure on the top of JBoss Logging.
To learn more about JBoss Logging we recommend the following articles:
Internal Logging
Configuring a Periodic Rotating File Handler
Configuring Handlers for single packages
Configuring Logging for a single application
How to read WildFly log files using the CLI
5 WildFly Loggers you should know about
Log4j Configuration
How to fix Log4j CVE-2021-44228
Configuring Log4j1 in your applications
Configuring Log4j2 in your applications
Configure Log4j in an EAR file
How to read WildFly logs using the CLI
In this short tutorial we will learn how to inspect the WildFly log files from the Command Line Interface.
How to fix Log4j CVE-2021-44228
This security bulletin discusses the recent flaws in Log4j2 library which affects some recent versions of this opensource library. Let’s see how to perform checks and mitigation actions if your Java applications are using a flawed Log4j2 version.
Configuring a Periodic Rotating File Handler
This article will teach you how to configure the Periodic File Handler in WildFly. We will also go through some common settings and advanced options such as compressing and rotating the logs file.
How do I enable debug logs in WildFly?
This tutorial will teach you how to change the default log level in WildFly using the management instruments available
Where are JBoss logs located?
We will shortly discuss where JBoss EAP / WildFly logs are located. The location of JBoss logs basically depends on which mode you are using to start the application server. View logs in standalone mode When running in standalone mode, JBoss logs are located in the standalone/log folder: As you can see, the currently running … Read more
5 WildFly Loggers you should know about
in WildFly and JBoss EAP Loggers are used to log messages by defining a category generally consisting of a package name or a class name. In short, they can let you customize the logging events for a package or Class name. We will see 5 Loggers which I’ve found pretty useful in my work. org.jboss.remoting.remote … Read more
Configuring a JBoss Handler which writes in a distinct file logs for a package
This article shows how to configure a JBoss Logging Handler for a specific package (category) to be written in a separate log file. Sometimes you need to add verbosity to a specific JBoss/WildFly package but you don’t want to mix it with the application server’s logs. So, in order to do that, you need to … Read more
How to configure log4j in your ear ?
This article is now obsolete. We recommend checking these resources to learn bout log4j configuration with JBoss / WildFly: How to use Log4j2 in your WildFly applications Using Log4J with WildFly and JBoss EAP Have you got exceptions when tried to configure log4j at application level ? this is due to the fact that JBoss ships … Read more
Create a Custom Camel logging handler for WildFly
A Custom logging handler allows you to define a custom destination for your WildFly / JBoss AS 7 server logging events. You would typically define a custom hanlder to log to a Socket, a Database, to a remote location or a JMS Queue. In this tutorial we will learn how to base your custom handler … Read more
