Yes, we had the same problem for a JBoss/Jetty 3.2.1/Lin installation. We didnt find the reason for this problem so we switched to use a JBoss/Tomcat configuration for that server.
I did some monitoring just to check the memory consumption and execution. Couldnt really find anything abnormal. The error condition also takes some time to reproduce. I dont have any deeper knowledge in Jetty so debug tracing would take some time. My guess is that some resources are not being returned correctly to the pool.
Please post if you find out how to work arounf this problem. It would be good to know.
If this is Linux, most probably your java.io.tempdir is set to /tmp, and Linux is clearing that occasionally.
Create a new tmp dir somewhere other than /tmp
Edit your $JBOSS_DIST/bin/run.conf file.
Add to the JAVA_OPTS the following:
You will have to restart JBoss, but this should fix your problem.
-Djava.io.tempdir=/some/path/to/new/tmp has an extra 'e' in tempdir, should be -Djava.io.tmpdir=/some/path/to/new/tmp
Thanks for the fix, works great.