[ http://issues.apache.org/jira/browse/QPID-37?page=all ]
Martin Ritchie resolved QPID-37.
--------------------------------
Fix Version/s: (was: M1)
Resolution: Invalid
Unrelated to JMX settings.
If using qpid-run the log4j.properties in client.jar is picked up before the
command line option as a result the log4j.properties file is used in
conjunction with the specified log4j.xml file.
> When starting the broker with JMX options Log4j settings are not honoured.
> --------------------------------------------------------------------------
>
> Key: QPID-37
> URL: http://issues.apache.org/jira/browse/QPID-37
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Priority: Minor
>
> To reproduce:
> Set log4j.properties to use a FileAppender Only
> either use qpid-server or run
> qpid-run org.apache.qpid.server.Main -c ../etc/config-file.xml
> then try setting JAVA_OPTS
> JAVA_OPTS="-Dcom.sun.management.jmxremote
> -Dcom.sun.management.jmxremote.port=8999
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false"
> and re-run
> qpid-run org.apache.qpid.server.Main -c ../etc/config-file.xml
> For completeness: I have been using qpid-server and qpid-server-jmx which
> simply has the JAVA_OPTS line added before the qpid-run call.
> When running with the JMX options you should see the logging output on the
> console. Which is not what the log4j properties specify.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
