How to change logging level using CLI command in JBoss EAP 6 ?

Solution Unverified - Updated -

Issue

  • How to change logging level using CLI command in JBoss EAP 6 ?
  • There seems to be a misconfiguration in the domain.xml/standalone.xml, how to enable logging on the specific package to determine or debug the issue in EAP 6?
  • logging subsystem and logging.properties are set to INFO as a minimum, yet seeing TRACE, DEBUG, FINE, FINER on module package names
  • How I can start the jboss in debug mode?
  • Thelog level should reflect automatically when logging level is changed without restart. I change log level from INFO to DEBUG. It is not reflecting without restart. How can we do without restart?
  • In JBoss EAP 4.x there was a configuration in jboss-services.xml when changes to log configuration come effective. Is there something similar in JBoss EAP 6.4? Do we have to reboot server every time when changing log level?
<mbean code="org.jboss.logging.Log4jService"
      name="jboss.system:type=Log4jService,service=Logging"
      xmbean-dd="resource:xmdesc/Log4jService-xmbean.xml">
      <attribute name="ConfigurationURL">resource:jboss-log4j.xml</attribute>
      <attribute name="Log4jQuietMode">true</attribute>
      <!-- How frequently in seconds the ConfigurationURL is checked for changes -->
      <attribute name="RefreshPeriod">60</attribute>
</mbean>

Environment

  • Red Hat JBoss Enterprise Application Platform(EAP)
    • 6.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
Close

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