[
https://issues.apache.org/jira/browse/JENA-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772389#comment-13772389
]
Andy Seaborne commented on JENA-536:
------------------------------------
There's a built-in log4j setup that is used if {{-Dlog4j.configuration}} is not
set.
It looks like there used to be a log4j.properties in some other jar or other
that is shaded into the server jar. Due to tidying up elsewhere (libraries
should not include a log4j.properties file), this is no longer put in the
server jar to include.
A fix might be to include {{-Dlog4j.configuration=file:...}} if and only if the
target file exists. That would allow the user to choose the logging format but
default to the built-in one.
> Missing log4j.properties
> ------------------------
>
> Key: JENA-536
> URL: https://issues.apache.org/jira/browse/JENA-536
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 1.0.0
> Reporter: Joachim Neubert
>
> On two different machines I run into a problem after upgrading from a Fuseki
> snapshot (June 28) to 1.0.0: Starting via "./fuseki start", I get:
> log4j:WARN No appenders could be found for logger
> (org.apache.jena.riot.stream.JenaIOEnvironment).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Strange thing is: When I define the before non-existing env variable
> JAVA_OPTIONS, omitting " -Dlog4j.configuration=log4j.properties", all works
> fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
