Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering JBoss Enterprise Application Platform 7

You're reading from   Mastering JBoss Enterprise Application Platform 7 Core details of the Enteprise server supported by clear directions and advanced tips.

Arrow left icon
Product type Paperback
Published in Aug 2016
Publisher Packt
ISBN-13 9781786463630
Length 390 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Luigi Fugaro Luigi Fugaro
Author Profile Icon Luigi Fugaro
Luigi Fugaro
Francesco Marchioni Francesco Marchioni
Author Profile Icon Francesco Marchioni
Francesco Marchioni
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Installation and Configuration FREE CHAPTER 2. The CLI Management Tool 3. Managing EAP in Domain Mode 4. Deploying Applications 5. Load Balancing 6. Clustering EAP 7 7. Logging 8. Configuring Database Connectivity 9. Configuring EAP 7 for Java EE Applications 10. Messaging Administration 11. Securing the Application Server 12. New Security Features of EAP 7 13. Using EAP 7 with Docker 14. Running EAP 7 on the Cloud Using OpenShift

Configuring loggers


Each time a log event is emitted, it contains information about the log level and the fully qualified class name bound to that event. In order to associate this information with a specific handler, you can use loggers.

Loggers are associated with a specific namespace, hence they have a hierarchy that contains, at the root, the root logger that is the ancestor of all loggers. All classes that don't have a configured logger will therefore be captured by the root logger. The root logger by default is associated with the CONSOLE and FILE handlers. You can vary it by specifying the list of Handlers as follows:

/subsystem=logging/root-logger=ROOT/:write-attribute(name=handlers,value=["CONSOLE","FILE","SYSLOG"])

By default, the root logger traces logs with the INFO (or higher) level. You can change at any time the root logger level through the change-root-log-level operation. For example:

/subsystem=logging/root-logger=ROOT/:change-root-log-level(level=WARN)

Defining new loggers...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime