[
http://jira.magnolia.info/browse/MAGNOLIA-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philippe Marschall updated MAGNOLIA-1597:
-----------------------------------------
Attachment: Log4jConfigurer.java.patch
Fix attached.
The problem is that you use the original, relative file name to configure log4j
which can't find it. What should be used instead is the in memory stream for
which variables have been replaced.
> Log4jConfigurer fails to locate log4j configuration file if property file
> format used
> -------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-1597
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1597
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 3.0.1
> Reporter: Konstantin Zadorozhny
> Assignee: Boris Kraft
> Attachments: Log4jConfigurer.java.patch
>
>
> There is a bug in Log4jConfigurer initLogging method. The
> PropertyConfigurator.configure(log4jFileName) call should use properties as a
> parameter.
> else {
> Properties properties = new Properties();
> try {
> properties.load(IOUtils.toInputStream(config));
> }
> catch (IOException e) {
> log("Unable to initialize Log4J from [" //$NON-NLS-1$
> + log4jFileName
> + "], got an Exception during reading the properties
> file " //$NON-NLS-1$
> + e.getMessage());
> return;
> }
> PropertyConfigurator.configure(log4jFileName); // FIXME
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
