Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty 7.4.4 using 100% CPU (apparently in SelectChannelConnector)
Hi Tony,

We have at least two bug reports opened in bugzilla for 100% CPU issues with connectors, Bug 351624 and Bug 351801, that you are welcome to chime in on if you feel that they are describing a similar problem. It would be helpful if you could also capture a thread dump of the server when it is running normally under similar conditions and post it along with the link to the dump below so that we could compare them.

Also, we recently developed a tool that has not been released yet that attempts to detect spinning and deadlocked threads, and dumps the information into the log file. You could build it from source code that is located here. There's a README.txt file in the top-level directory that describes how to install and run this tool. If you could get the log file with the tool's output to us, it would be a great help in diagnosing this issue.

-Michael

On Thu, Jul 28, 2011 at 9:58 PM, Tony Arcieri <tony@xxxxxxxxxxxxxx> wrote:
Hi, seems like this is something of a long standing problem (JETTY-937) but we're seeing it on the latest release of Jetty. I saw this thread which appeared to be a similar issue with SslSocketConnector:


Our problems were much worse with Jetty 7.4.2. Jetty 7.4.4 seemed to improve things, to where we're seeing the problem far less frequently, but it's still there. Rolling back to Jetty 7.3.1 seems to have fixed our problems, AFAICT.

Here's a thread dump of one of our JVMs in the 100% CPU state:


All threads are blocked except Jetty's acceptor threads, which are consuming 100% CPU.

--
Tony Arcieri
Strobe Inc.


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users


Back to the top