-
Edit
$RUNTIME/jboss/bin/jboss-cli.shto enable logging invamessages.log.Note: You need not restart the site for JBoss to pick up these changes. -
To change log levels, as a root user, perform the following:
-
To enable debug logging, run the following command:
/subsystem=logging/root-logger=ROOT:change-root-log-level(level=DEBUG) -
To disable debug logging, run the following command:
/subsystem=logging/root-logger=ROOT:change-root-log-level(level=INFO)
-
-
To change log levels using your LDAP credentials, perform the following:
-
To enable debug logging, run the following command:
/subsystem=logging/logger=com.vasoftware:write-attribute(name="level", value="DEBUG") -
To disable debug logging, run the following command:
/subsystem=logging/logger=com.vasoftware:write-attribute(name="level", value="INFO") -
To enable trace logging for LDAP, run the following command:
/subsystem=logging/logger=org.jboss.security.auth.spi.LdapExtLoginModule:add(level=TRACE,handlers=["VAFILE"]) -
To disable trace logging for LDAP, run the following command:
/subsystem=logging/logger=org.jboss.security.auth.spi.LdapExtLoginModule:remove()Tip: The LDAP debug output will be very limited unless you add <module-option name=throwValidateErrorsvalue=true></>to the entry for the corresponding log-in module.
-
-
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.
Note: Changes are immediately saved toruntime/jboss/standalone/configuration/standalone-full.xml and the file,standalone-full.xmlis recreated every time the TeamForge runtime is rebuilt. -
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.