You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (Assigned) (JIRA)" <ji...@apache.org> on 2012/01/16 16:44:40 UTC
[jira] [Assigned] (QPID-3761) rename the Java brokers fallback
log4j properties file to prevent unexpected usage
[ https://issues.apache.org/jira/browse/QPID-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reassigned QPID-3761:
------------------------------------
Assignee: Keith Wall (was: Robbie Gemmell)
Hi Keith,
could you review these changes please?
Thanks,
Robbie.
> rename the Java brokers fallback log4j properties file to prevent unexpected usage
> ----------------------------------------------------------------------------------
>
> Key: QPID-3761
> URL: https://issues.apache.org/jira/browse/QPID-3761
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.14
> Reporter: Robbie Gemmell
> Assignee: Keith Wall
> Priority: Minor
> Fix For: 0.15
>
>
> The Java broker has a fallback configuration for Log4J, which is named log4j.properties and gets included in the broker jar file. this file can be picked up automatically by Log4J when it scans the classpath for configuration. When this jar is in the main qpid/java/build folder this fallback configuratiopn can be picked up when running examples etc and result in the use of debug logging. The file should possibly just be removed, but at the very least it should not be named log4j.properties to ensure this does not occur.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org