?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
--
View this message in context:
http://old.nabble.com/Tomcat-100--CPU-usage-after-moving
..
--
View this message in context:
http://old.nabble.com/Tomcat-100--CPU-usage-after-moving-from-Java-5-to-6-tp27305110p27416818.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users
Well, as I said, Tomcat is working much more stable now than it did before.
However, once in a few days it still becomes unresponsive, while CPU usage
stays incredibly low.
Unresponsive, meaning what, exactly? If the CPU is idle, but your
webapp isn't returning a response... it seems to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse,
On 2/2/2010 3:23 AM, Jesse Klaasse wrote:
Christopher Schultz-2 wrote:
Can you give us a timestamp for when the trouble started? Reading GC
output is pretty tedious.
I believe the trouble started around 15 - 20 minutes before the end
://old.nabble.com/Tomcat-100--CPU-usage-after-moving-from-Java-5-to-6-tp27305110p27402032.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse,
On 2/1/2010 5:22 AM, Jesse Klaasse wrote:
In the meantime, the environment has been much more stable than it was before
the move to Java 6 and the new JVM options. However, a few minutes ago,
Tomcat became completely unresponsive, while
some research to be done.
In the meantime I am very pleased with the results. Tomcat's CPU usage seems
significantly lower than before (it's average seems about 10% now - which
was 30-40% before) - scary!
--
View this message in context:
http://old.nabble.com/Tomcat-100--CPU-usage-after-moving
Jesse Klaasse wrote:
I have now fixed the infinite loop, and again did the update from Java 5 to
Java 6. This time all seems to be working like a charm!
Along with fixing the infinite loop, I have dug a little deeper into the JVM
arguments. I found the following article particularly useful:
://java.sun.com/javase/technologies/hotspot/vmoptions.jsp
I thought, I'd just let you all know!
--
View this message in context:
http://old.nabble.com/Tomcat-100--CPU-usage-after-moving-from-Java-5-to-6-tp27305110p27322864.html
Sent from the Tomcat - User mailing list archive at Nabble.com
From: Jesse Klaasse [mailto:jesse.klaa...@indicia.nl]
Subject: Re: Tomcat 100% CPU usage after moving from Java 5 to 6
I found the following article particularly useful:
http://confluence.atlassian.com/display/DOC/Garbage+Collector+Performance+Issues
Unfortunately, that article is so full
--CPU-usage-after-moving-from-Java-5-to-6-tp27305110p27324793.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h
On Tue, Jan 26, 2010 at 4:50 PM, Jesse Klaasse jesse.klaa...@indicia.nl wrote:
Hi Chuck, thanks for your extensive comments about the JVM options..
On a site note... I have made the observation that the JVM is
performing best without any explicit gc settings. Most time explicit
GC settings
2010/1/26 Leon Rosenberg rosenberg.l...@googlemail.com
Another customer of mine was playing with gc settings for nearly a
year, because his tomcats collection times went higher and higher, and
after a short look at the heap dump with jmap and jhat, we found out
that he had 100.000.000
On 25/01/2010 11:08, Jesse Klaasse wrote:
I am running a production environment for a website (over half a million
hits per day), using Tomcat 5.5.20 (I'm stuck to that version due to
support restrictions) behind IIS 6 using JK connector 1.2.28,
tcnative-1.dll (1.1.19) on Windows Server 2003 R2
take a look on threads
ajp-8009-2
ajp-8009-18
ajp-8009-30
ajp-8009-38
they are all seem to be either in an infinite loop:
at java.util.AbstractList$Itr.hasNext(AbstractList.java:339)
at
nl.indicia.vip.framework.util.Workflow.performWorkflowAction(Workflow.java:166)
at
P.S. Your tomcat is writing gc logs, please attach them next time.
On Mon, Jan 25, 2010 at 12:31 PM, Leon Rosenberg
rosenberg.l...@googlemail.com wrote:
take a look on threads
ajp-8009-2
ajp-8009-18
ajp-8009-30
ajp-8009-38
they are all seem to be either in an infinite loop:
at
it correctly), and it's overwritten when Tomcat is restarted, so
there's really nothing I can say about that. Do you suspect any problems
there?
--
View this message in context:
http://old.nabble.com/Tomcat-100--CPU-usage-after-moving-from-Java-5-to-6-tp27305110p27305900.html
Sent from the Tomcat - User
in DQWorkflow is not
synchronized and uses Vectors and Iterators. Could this be a possible
problem? Even though this all has been working perfectly fine in Java 4 and
5?
--
View this message in context:
http://old.nabble.com/Tomcat-100--CPU-usage-after-moving-from-Java-5-to-6-tp27305110p27305988.html
Workflow.java
--
View this message in context:
http://old.nabble.com/Tomcat-100--CPU-usage-after-moving-from-Java-5-to-6-tp27305110p27306041.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
/file/p27306041/DQWorkflow.java DQWorkflow.java
http://old.nabble.com/file/p27306041/Workflow.java Workflow.java
--
View this message in context:
http://old.nabble.com/Tomcat-100--CPU-usage-after-moving-from-Java-5-to-6-tp27305110p27306041.html
Sent from the Tomcat - User mailing list archive
());
}
and you are modifying this vector at multiple places in the same class.
You should probably unit-test this code for concurrency.
regards
Leon
--
View this message in context:
http://old.nabble.com/Tomcat-100--CPU-usage-after-moving-from-Java-5-to-6-tp27305110p27306543.html
Sent from
Jesse Klaasse wrote:
...
ctory -Dcom.sun.management.jmxremote -XX:MaxPermSize=512m
-Xloggc:D:\logs\gc\tomcat-gc.log -XX:+PrintGCDetails -XX:+UseParNewGC
-XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:+CMSClassUnloadingEnabled
-XX:+CMSPermGenSweepingEnabled -Xms4096m -Xmx10240m
Apart from your
Jesse Klaasse wrote:
Hi Leon,
I don't know what you mean exactly by re-intrant, but your comment points
out I have created an endless while-loop! Apart from moving to Java 6, I had
commented out some lines to reduce logging, not noticing I had created an
endless loop by doing so. I only did
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse,
On 1/25/2010 8:25 AM, Jesse Klaasse wrote:
I don't know what you mean exactly by re-intrant
Re-entrant (never seen it as re-intrant) means that more than one
thread of execution might be running the same code concurrently. I've
never heard
24 matches
Mail list logo
