https://bugzilla.redhat.com/show_bug.cgi?id=845993
Bug ID: 845993
QA Contact: extras-qa(a)fedoraproject.org
Severity: high
Version: 17
Priority: unspecified
CC: java-sig-commits(a)lists.fedoraproject.org,
kdaniel(a)redhat.com, mizdebsk(a)redhat.com,
overholt(a)gmail.com, sochotni(a)redhat.com
Assignee: sochotni(a)redhat.com
Summary: Jetty unpacks deployed apps to /tmp which get cleaned
up by systemd-tmpfiles
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: owen(a)fraser-green.com
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: jetty
Product: Fedora
Description of problem:
After running a Jetty app for some days without problem, it may suddenly give
HTTP 404 messages serving static content, and java.lang.NoClassDefFoundError
exceptions for dynamic content. Closer investigation reveals that, while the
files were present in the WAR file, the WAR file has been unpacked to
/tmp/jetty-0.0.0.0-<something> and some of the contents have disappeared. While
I don't have evidence that systemd-tmpfiles is responsible, I see it's
configured to delete files in /tmp after 10 days so I assume it's the culprit.
Version-Release number of selected component (if applicable):
jetty-8.1.2-9
systemd-44-17
How reproducible:
If my assumption as to the cause are correct, this will occur in most cases a
Jetty app is deployed after 10 days.
Steps to Reproduce:
1. Deploy a Jetty app
2. Wait
Actual results:
Jetty serves HTTP 404 messages instead of content.
Expected results:
The actual content is served.
Additional info:
I worked around by simply creating the directory /usr/share/jetty/work/
As per
http://wiki.eclipse.org/Jetty/Reference/Temporary_Directories Jetty will
the create it's working directory under here. While this work around is fine
for me, I believe a better place for the work directory would be under /var,
perhaps /var/lib/jetty/work.
--
You are receiving this mail because:
You are on the CC list for the bug.