[
https://issues.apache.org/jira/browse/JENA-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229519#comment-17229519
]
Andy Seaborne commented on JENA-1989:
-------------------------------------
Mislabelled commit:
-------------------
Commit da2e8ddc3c833a94687d2b2ec2cbe1909151f36f in jena's branch
refs/heads/master from Andy Seaborne
[ [https://gitbox.apache.org/repos/asf?p=jena.git;h=da2e8dd] ]
JENA-1898: Log output for webapp
> No log output with Fuseki+Tomcat9+Systemd
> ------------------------------------------
>
> Key: JENA-1989
> URL: https://issues.apache.org/jira/browse/JENA-1989
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Jena 3.16.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 3.17.0
>
>
> Running Fuseki and Tomcat9 with systemd shows a number of problems:
> # /etc/fuseki/ is not accessible - Tomcat9 with systemd is sandboxed and
> /etc/fuseki is not writable. (Fix: document that systemd needs configuring).
> # Log output handled differently. systemd captures stdout and sends it to
> the system journal. There is no catalina.out. (Fix: document how to setup
> systemd)
> # log4j2 setup happens as the webapp starts and before Fuseki initialization
> is called. Result - the Fuseki configuration is not used. Fix: Use the
> log4j-web artifact and configure web.xml.
> The servlet/log setup probably applies to Fuseki logging for log4j2 in
> Tomcat8 as well but I can't install the stabndard setupo of tomcat8 and
> systemd because it is no longer available in the Ubuntu repos (Ubuntu 20.10).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
