Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] When does a Jetty thread exactly become idle?

Hi Joakim,

Here's the detail.

Full version of Jetty

full version of your JDK
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)

what is your environment OS/Arch?
Linux 2.6.18-238.el5

The connections you are referring to are doing what?

It does normal servlet that accepts REST requests.


On Fri, Dec 13, 2013 at 12:18 AM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
More specifics on the versions please.  
Full version of Jetty, and full version of your JDK.
Also, what is your environment OS/Arch?

The connections you are referring to are doing what?
Normal servlet?
Async servlet?

Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts

On Thu, Dec 12, 2013 at 7:41 AM, Takenori Sato <tsato@xxxxxxxxxxxx> wrote:

I have a case that CLOSING state socket remains.

And I wonder if this could have led to long latency in Jetty.
For example, as more and more CLOSING state sockets get piled up,
and reaches to maxThreads, then new requests won't get processed until they are cleaned up.

So, when does a Jetty thread become idle, exactly?
If it is soon after sending FIN, CLOSING state won't be an issue.

I have looked through the source code, 
also like bug 364921, but didn't get any clue.
Can you suggest where to look at?

My environment:


jetty-users mailing list

jetty-users mailing list

Back to the top