How to avoid hardcoded logging.properties name in EAP6.1

Solution Unverified - Updated -

Issue

  • As in "logging.properties" fileName is hardcoded in the "$JBOSS_HOME/bin/standalone.sh" script as following:
while true; do
   if [ "x$LAUNCH_JBOSS_IN_BACKGROUND" = "x" ]; then
      # Execute the JVM in the foreground
      eval \"$JAVA\" -D\"[Standalone]\" $JAVA_OPTS \
         \"-Dorg.jboss.boot.log.file=$JBOSS_LOG_DIR/server.log\" \
         \"-Dlogging.configuration=file:$JBOSS_CONFIG_DIR/logging.properties\" \
  • So if multiple JBoss profiles like "$JBOSS_HOME/standalone_1" , "$JBOSS_HOME/standalone_2" and "$JBOSS_HOME/standalone_3" wanted to have their own logging.properties with some different name like following then how can it be achieved.
    "$JBOSS_HOME/standalone_1/configuration/logging_1.properties"
    "$JBOSS_HOME/standalone_2/configuration/logging_2.properties"
    "$JBOSS_HOME/standalone_3/configuration/logging_3.properties"

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 6.1

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.