Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty 9.3.10.v20160621 stops rendering static content

Just a guess, but the shibboleth war was probably unpacked into your /tmp directory (used as a jetty working directory).
Then the /tmp directory was cleaned up by some other process, rendering the working directory invalid.

Either set the working / temp directory for your webapp to somewhere other then
or specify an alternate location for
or create a ${jetty.base}/work directory

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Fri, Jan 6, 2017 at 3:35 AM, Shagun Akarsh <shagun.akarsh@xxxxxxxxxx> wrote:

We have deployed Shibboleth IdP v3.2.1  war on jetty.

Everything works fine, but jetty 9.3.10.v20160621 (JETTY-HOME=/usr/local/jetty-distribution-9.3.10.v20160621) started sending 404 response to all static content (js/css/images) after running the server for more than a week. After restarting jetty server it again started serving static content properly.

Jetty log: java.util.concurrent.TimeoutException: Idle timeout expired: 30000/30000 ms

I am new to jetty community, What could be the possible reason ? Is it specific to jetty configuration ?

Shagun Akarsh
Ph: +91-9902095371

jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top