Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty refuses to accept new request

Without stacktraces to go on, I would have to speculate.

My first guess would be that you are relying on /tmp for your temporary & work directories.
The problem you describe is a behavior seen on many unix systems where the contents of the /tmp directory are cleared out occasionally by various cronjobs.
Using /tmp is a behavior seen on many unix systems as the System.getProperty("") often returns this location (but not on all unix systems and configurations).
The "" directory is used by jetty to unpack war files into and run the war file from, if that directory gets cleared out from under jetty then jetty stops processing requests to that context.

You can solve this in one of two ways.

Way 1:
Create a ${jetty.home}/work directory.
By default jetty will use this directory for unpacking war files into (if it exists).

Way 2:
Specify the temp directory.
Using the DeploymentManager + WebAppProvider you can specify the "tempDir" property to somewhere more stable.
Example of this configuration can be seen in the test cases in jetty.

Joakim Erdfelt
joakim@xxxxxxxxxxx |
(the people behind jetty and cometd)

On Fri, Jan 6, 2012 at 8:25 AM, Peter Henzler <phe@xxxxxxxx> wrote:

Hi everyone


We have Jetty embedded in our eclipse osgi server application.

Everything worked fine until we upgraded to using Jetty 7.5.4.v20111024 and Java 7.


Now we have serious troubles with our application.

From one moment to the other the web server does not accept new requests.
That means users connecting new to the server do not get a response from the server. It seems as if the call is hanging at the server side.
First we thought this could be a memory issue.

But we found out that this is not the case.

Users that to have their sessions can happily work and the server handles their request without problems.

It looks as if the web server cannot accept requests from clients that are new.


We are booting our application every morning now.

Sometimes the server is up for 2-3 days until this issue occurs.
But sometimes this happens already 2 hours after starting.

So it seems that it has nothing to do with workload, memory usage or computer resources.


We are totally desperate and hope that somebody can give us a hint, what might be the problem.


Best regards from Switzerland

Peter Henzler

jetty-users mailing list

Back to the top