Message-ID: <1684293438.19406.1406748753674.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_19405_145633853.1406748753674" ------=_Part_19405_145633853.1406748753674 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
So, your webapp is humming along nicely when suddenly it stops working, =
and your log files are full of exceptions. You may see log entries for styl=
e sheet files not found, compiled JSP classes not being found or some other=
static content missing. The most frequent culprit on Unix systems is a
This is bad news for a web-app because Jetty stores various kinds of fil= es associated with it into this temporary location. For example, if your we= b-app is deployed as a war file, Jetty will uncompress it and run it from t= he tmp directory. If your web-app also uses non-precompiled JSPs, then the = generated class files also go into this tmp directory. Each web-app is give= n its own directory under the tmp location, named according to the context = and port number, eg:=20 =20
Either disable the cron job, or (more conscientiously) redefine the top = level tmp directory. To redefine your temporary directory location see Temporary Directories.