Some additional infos: root@phobos ~ # uname -a Linux phobos 2.6.32-6-pve #1 SMP Mon Jan 23 08:27:52 CET 2012 x86_64 GNU/Linux
root@phobos [...] # ./java -version java version "1.7.0_03" Java(TM) SE Runtime Environment (build 1.7.0_03-b04) Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode) -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Maximilian Böhm Sent: Tuesday, May 22, 2012 2:51 PM To: [email protected] Subject: [jetty-users] Jetty5: CPU-Usage Problem Hi Guys, We are running jetty5 on approximately ~50 server upwards. Mostly there are more than 40 virtualhosts on a machine. Now we have a 100% cpu-usage on two of this servers. We already switched the hardware to virtualisation and now I replaced all regulary programfiles from files of a working server. Through ps -eLf and jstack I found the following (never ending) Thread: "SocketListener0-7" prio=10 tid=0x0000000001eb7000 nid=0x5d7a runnable [0x00007f569b2fc000] java.lang.Thread.State: RUNNABLE at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:782) - locked <0x00000000d1b33c60> (a java.lang.IllegalMonitorStateException) at java.lang.Throwable.<init>(Throwable.java:250) at java.lang.Exception.<init>(Exception.java:54) at java.lang.RuntimeException.<init>(RuntimeException.java:51) at java.lang.IllegalMonitorStateException.<init>(IllegalMonitorStateException.java:50) at org.mortbay.util.DateCache.format(DateCache.java:250) - locked <0x00000000ddc05c90> (a org.mortbay.util.DateCache) at org.mortbay.http.HttpRequest.getTimeStampStr(HttpRequest.java:154) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:937) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) What can cause this? I know, jetty5... Upgrading and so on. We work on it. We made a mistake ealier, integrating jetty too deep into our software... Best regards & Thanks Max Böhm _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
