Loading...

XML

Word

Printable

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

EAP73 7.3.0.GA
Workaround:

Workaround Exists
Workaround Description:
Hide

Either

During a container build step, copy a version of the /opt/eap/standalone/configuration/logging.properties file into the resulting container. The /opt/eap/standalone/configuration/logging.properties file should include the level set to INFO instead of DEBUG.
OR

Remove the /opt/eap/standalone/configuration/logging.properties file as part of a container build. However, this may have unwanted side effects wrt missing information in the logs for certain items.
Show
Either During a container build step, copy a version of the /opt/eap/standalone/configuration/logging.properties file into the resulting container. The /opt/eap/standalone/configuration/logging.properties file should include the level set to INFO instead of DEBUG. OR Remove the /opt/eap/standalone/configuration/logging.properties file as part of a container build. However, this may have unwanted side effects wrt missing information in the logs for certain items.

The EAP 7.x image contains a /opt/eap/standalone/configuration/logging.properties file that sets

logger.org.jboss.as.config.level=DEBUG

This can expose sensitive data to log files when EAP starts up, before the EAP logging subsystem is initialized.

Can we remove the /opt/eap/standalone/configuration/logging.properties file altogether or default this to INFO instead?