[
https://issues.jboss.org/browse/JBAS-9049?page=com.atlassian.jira.plugin....
]
David Lloyd commented on JBAS-9049:
-----------------------------------
If we supported nested property resolution in logmanager we could do something like this:
handler.FILE.fileName=${jboss.boot.log.file:${jboss.server.log.dir:${jboss.server.base.dir:${jboss.home.dir:.}/standalone}/log}/boot.log}
This actually would be pretty easy to add to logmanager - 3-4 lines of changes probably.
Need way to override the boot.log in start scripts
--------------------------------------------------
Key: JBAS-9049
URL:
https://issues.jboss.org/browse/JBAS-9049
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: 7.0.0.Beta1
Reporter: Scott Stark
Assignee: David Lloyd
Original Estimate: 1 hour
Remaining Estimate: 1 hour
We need the ability to specify the location of the boot.log. Right now the boot.log
location is specified via the org.jboss.boot.log.file java system property, but this is
always set to $JBOSS_HOME/standalone/log/boot.log in the server start scripts. This should
either not be set and simply default to $JBOSS_HOME/standalone/log/boot.log when unset so
that it may be passed into the jvm, or, we need a JBOSS_BOOT_LOG env property that can
override this value along the line of:
if [ "x$JBOSS_BOOT_LOG" = "x" ]; then
JBOSS_BOOT_LOG="$JBOSS_HOME/standalone/log/boot.log"
fi
while true; do
if [ "x$LAUNCH_JBOSS_IN_BACKGROUND" = "x" ]; then
# Execute the JVM in the foreground
eval \"$JAVA\" $JAVA_OPTS \
\"-Dorg.jboss.boot.log.file=$JBOSS_BOOT_LOG\" \
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira