[
https://issues.jboss.org/browse/AS7-2314?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-2314:
----------------------------------
Fix Version/s: 7.1.0.CR1
(was: Open To Community)
Assignee: David Lloyd (was: Jason Greene)
David, I'm assigning this to you because I saw you say something about changing how
boot logging works. So if your changes eliminate this whole area, you can close this. :-)
If not, feel free to unassign and move to Open to Community.
The key issue is -D values passed after ./standalone.sh are args to main and not to the
JVM. So they are too late for boot logging config; setting them in standalone.conf is
necessary. Just complicated and confusing. We could probably improve a bit, but if the
whole boot vs server log thing will go away, all the better.
Passing -Djboss.boot.server.log.level=DEBUG to standalone.sh script
is ignored
------------------------------------------------------------------------------
Key: AS7-2314
URL:
https://issues.jboss.org/browse/AS7-2314
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.1.0.Alpha1
Environment: Fedora 14, java-1.6.0-openjdk, jboss-as-7.1.0.Alpha2-SNAPSHOT
Reporter: Rich Lucente
Assignee: David Lloyd
Priority: Minor
Labels: eap6-ux
Fix For: 7.1.0.CR1
Attempting to change boot log level via a script argument to standalone.sh is ignored. I
can edit standalone.conf (set value in JAVA_OPTS) or edit logging.properties directly.
Other -D parameters are honored, so there seems to be some startup/timing issue with this
specific setting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira