Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Error with shibboleth-idp and jetty

This is the source of your Apache Jasper warning ...

2017-04-20 05:50:06.059:WARN:oaj.EmbeddedServletOptions:qtp987405879-11: The  scratchDir you specified: /tmp/jetty- is unusable.

Your /tmp/jetty- path fails one of the following checks ....
  • must exist
  • is a directory
  • jetty user should be able to read from that directory
  • jetty user should be able to write to that directory
Does this happen immediately? or after some time?

If it happens after some time, then you likely have a process on your unix server that is periodically cleaning up the /tmp/ directory (which broke jetty).

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Fri, May 19, 2017 at 3:26 AM, Pritha Srivastava <prsrivas@xxxxxxxxxx> wrote:

We have a setup that has a shibboleth-idp with a jetty server. Any requests to the shibboleth-idp is returning an error. I issued the following command:

curl -kvL https://<hostname>/idp and instead of seeing the expected result, I see errors like:


 http-equiv="Content-Type" content="text/html;charset=utf-8"/>
 Error 500 Server Error

 Problem accessing /idp/. Reason:
 <pre>    Server Errorpre>Caused
 by:<pre>java.lang.IllegalStateException: Not valid for write:
 id=node0xzkusdg1igdt4hol48y607u66 not resident

Looking at some older logs, I could see an error, after which similar errors started appearing:

2017-04-20 05:50:06.059:WARN:oaj.EmbeddedServletOptions:qtp987405879-11:
 The  scratchDir you specified:
 /tmp/jetty- is
 2017-04-20 05:50:09.289:WARN:/idp:qtp987405879-11: unavailable
         at org.apache.jasper.servlet.JasperLoader.loadClass(
         at org.apache.jasper.servlet.JasperLoader.loadClass(

I have checked permissions for the scratch directory, and they seem to be fine. I have also restarted shibboleth-idp several times, but that doesn't seem to solve the problem.
Everytime I issue a request to the idp, I get back the same error as above

Does anyone have any idea as to what has gone wrong and what can be done to solve this issue? (Maybe, rebuild the WAR file?)

Thanks in advance,

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

Back to the top