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 java.io.tmpdir
or specify an alternate location for java.io.tmpdir
or create a ${jetty.base}/work directory
Joakim Erdfelt / [email protected]
On Fri, Jan 6, 2017 at 3:35 AM, Shagun Akarsh <[email protected]>
wrote:
> Hello,
>
> 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.io.IOException: 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 <+91%2099020%2095371>
> Wooqer,
> Bangalore.
>
> _______________________________________________
> 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
