Installing JBoss LogManager on standalone (i.e. non-EAP) clients/JVMs
Issue
- How do I install JBoss LogManager on non-EAP JVMs?
- I want to configure a logging feature that's not available or is not convenient to configure via
java.util.logging
APIs. -
Since we upgrade to JBoss EAP 6.2 our client application stops logging. After our investigation, we found that JBoss EAP 6.2 client jars is packaged with jboss-logmanager-1.0.2.GA-redhat-1.jar instead of slf4j-log4j12-1.7.5.jar.
We tested by swapping out jboss-logmanager-1.0.2.GA-redhat-1.jar with slf4j-log4j12-1.7.5.jar, and our client application is able to log again.
We'd like to know by doing so would it cause any issue with JBoss client.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP) 6.x
- Standalone Java applications
- JBoss LogManager
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.