Set the logging level appropriately to enable logging in vamessages.log.
  1. Edit $RUNTIME/jboss/bin/jboss-cli.sh to enable logging in vamessages.log.

  2. To change log levels, as a root user, perform the following:

    1. To enable debug logging, run the following command:

      /subsystem=logging/root-logger=ROOT:change-root-log-level(level=DEBUG)
      
    2. To disable debug logging, run the following command:

      /subsystem=logging/root-logger=ROOT:change-root-log-level(level=INFO)
      
  3. To change log levels using your LDAP credentials, perform the following:

    1. To enable debug logging, run the following command:

      /subsystem=logging/logger=com.vasoftware:write-attribute(name="level", value="DEBUG")
      
    2. To disable debug logging, run the following command:

      /subsystem=logging/logger=com.vasoftware:write-attribute(name="level", value="INFO")
      
    3. To enable trace logging for LDAP, run the following command:

      /subsystem=logging/logger=org.jboss.security.auth.spi.LdapExtLoginModule:add(level=TRACE,handlers=["VAFILE"])
      
    4. To disable trace logging for LDAP, run the following command:

      /subsystem=logging/logger=org.jboss.security.auth.spi.LdapExtLoginModule:remove()
      



  • Change in log levels will not need any site restart and these changes will not survive the JBOSS restart.

  • Changes made using CLI will survive a restart but not a runtime recreation.

  • To retain the configurations after the site restart, edit $RUNTIME/jboss/standalone/configuration/standalone-full.xml.

  • To make the configurations survive the recreate runtime, edit $SITE_DIR/dist/conf-snippets/jboss/standalone-full.xml.d/20-standalone-full.xml.py.