Logback conflict with container's Log4J implementation during deployment of WAR

Solution Verified - Updated -

Issue

While deploying application WAR in Red Hat JBoss Enterprise Application Platform - 7.0 on Windows server using Management Console, observed that LogBack API is getting conflicted with container's internal Log4J API. Where the same WAR file is deployed on a JBOSS EAP 7.0 installation running on a Linux server, the deployment is successful without any changes.

If I need to keep the both modules(LogBack and Log4J), how do I remove the Logback?

Environment

  • Red Hat JBoss Enterprise Application Platform
    • 7.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content