JBoss not starting after logging configuration change, with log4j warning: Continuable parsing error

Solution Verified - Updated -

Issue

  • Although we have configured a custom appender (that is running ok), we have a warning on the server.log:
log4j:WARN Continuable parsing error 326 and column 23  
log4j:WARN The content of element type "log4j:configuration" must match "(renderer\*,appender\*,(category|logger)\*,root?,categoryFactory?)".
  • JBoss servers are not coming up when we change logging level to INFO from DEBUG in jboss-log4j.xml

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 4.x
    • 5.x
  • Red Hat JBoss Enterprise SOA Platform (SOA-P)
    • 4.x
    • 5.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.