[
https://issues.apache.org/jira/browse/JENA-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772648#comment-13772648
]
Joachim Neubert commented on JENA-536:
--------------------------------------
So probably the issue simply could be fixed by
diff --git a/fuseki b/fuseki
index e99804b..8b9de4a 100755
--- a/fuseki
+++ b/fuseki
@@ -205,7 +205,7 @@ fi
# Some JVM settings
if [ -z "$JAVA_OPTIONS" ]
then
- JAVA_OPTIONS="-Dlog4j.configuration=log4j.properties -Xmx1200M"
+ JAVA_OPTIONS="-Xmx1200M"
fi
> 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
