Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-3553

(CD20) Server fail to start when CONFIG_IS_FINAL is enabled and user does not supply a default logging.properties file

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP CD 20.0.GA
    • None
    • None
    • None

      The intention of CONFIG_IS_FINAL environment variable is to skip the server configurations activated by environment variables or by placeholder replacements.

      This environment variable can be used when the user wants to supply its own server configuration and this configuration should be considered as final.

      However, the scripts also replace by default the logging.properties file, specifically it sets the default logging formatter to COLOR-PATTERN. This formatter configuration is done by a placeholder replacement.

      When CONFIG_IS_FINAL is true, user has to supply the final stanadalone-openshift.xml file and the initial logging.properties file which enables the logging at the very first steps on the server boot phase.

      I initially open this as a bug since we can supply the default configuration to avoid the users to supply the stanadalone-openshift.xml and the logging.properties.

            yborgess1@redhat.com Yeray Borges Santana
            yborgess1@redhat.com Yeray Borges Santana
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: