There is always a temp directory on any modern OS, so your OPS are not understanding the question.
What you can do is explicitly state what directory Java will use as a temporary directory (by default, it uses the systems standard one). Where you launch your jetty, you can explicitly define the system property 'java.io.tmpdir': $ java -Djava.io.tmpdir=/a/safe/place/for/temp/files ... On Mon, Feb 9, 2015 at 2:34 PM, Eduardo Fiss Beloni <[email protected]> wrote: > Thank you for the reply Stefan, > > But the people that set up the servers told me there's no tmp clean up. > Can you think of another reason? > > Eduardo Fiss Beloni > [email protected] > www.voiza.com.br > Soluções em Java > (51) 4063-8913 - Porto Alegre > (53) 4062-9183/3222-1833 - Pelotas > > ----- Original Message ----- > From: "Stefan Magnus Landrø" <[email protected]> > To: "JETTY user mailing list" <[email protected]> > Sent: Wednesday, January 28, 2015 10:12:04 AM > Subject: Re: [jetty-users] Unable to render Velocity Template > > > > > Sounds like the linux tmp folder is cleaned up every now and then. You can > make jetty use a different tmp folder in order to prevent issue. See docs. > > Stefan > > > > 2015-01-28 12:26 GMT+01:00 Eduardo Fiss Beloni < [email protected] > : > > > Hello, > > We are having loads of "Unable to render Velocity Template" throughout the > jetty logs. Then the user can't see the site anymore. > > 2015-01-26 10:20:38,751 [qtp399631128-23 ERROR CommonsLogger]: Unable to > render Velocity Template, '/error.vm' > org.apache.velocity.exception.VelocityException: Exception rendering > #parse(/_inc/footer.vm) at /error.vm[line 67, column 9] > ... > ... > 2015-01-25 23:07:34,732 [qtp1819130381-4849 ERROR CommonsLogger]: Unable > to render Velocity Template, '/super/aba_vitrine.vm' > org.apache.velocity.exception.VelocityException: VelocimacroProxy.render() > : exception VM = #produto() > > It happens a few times a month. When this happens the only way to bring > our frontend servers back is to restart jettys. > > This started to happen when we updated from jetty 7 to jetty 9.1.3. Could > this be a jetty parameter or something? > > Thank you, > > Eduardo Fiss Beloni > [email protected] > www.voiza.com.br > Soluções em Java > (51) 4063-8913 - Porto Alegre > (53) 4062-9183/3222-1833 - Pelotas > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > > > -- > > BEKK Open > http://open.bekk.no > > > TesTcl - a unit test framework for iRules > http://testcl.com > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > -- - michael dykman - [email protected] May the Source be with you.
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
