Performance issue with Tomcat 5.0
In our application , jboss app server , fiorano messaging server , Tomcat 5.0 webserver , first time when give load of 200 users it works fine , but after some time 10 min , the tomcat server remains 48% idle , when there is no load , when i type top command it shows java process taking 99 % cpu , where is issue , how to resolve it , in application , applets are running at client side ? is that due to applet , how i should debug -- View this message in context: http://www.nabble.com/Performance-issue-with-Tomcat-5.0-t1442675.html#a3895859 Sent from the Tomcat - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Performance issue with Tomcat 5.0
I already done that dump using that kill quit command but how can i identify the problem , following is the thread dump , please help me how to look into Full thread dump Java HotSpot(TM) Client VM (1.5.0_05-b05 mixed mode, sharing): "Thread-1500" prio=1 tid=0xac187838 nid=0x2b85 waiting on condition [0xab4e6000..0xab4e7030] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:146) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1808) at java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:396) at com.hedgeflex.core.common.event.EventPublisher.run(EventPublisher.java:75) "Thread-1497" prio=1 tid=0xb23c9f38 nid=0x2ad9 waiting on condition [0xad1f7000..0xad1f7eb0] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:146) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1808) at java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:396) at com.hedgeflex.core.common.event.EventPublisher.run(EventPublisher.java:75) "http-80-Processor1464" daemon prio=1 tid=0x08536690 nid=0x2135 in Object.wait() [0xaebaa000..0xaebab0b0] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656) - locked <0x8a6fa5f0> (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:595) "http-80-Processor1463" daemon prio=1 tid=0x080c1150 nid=0x2134 in Object.wait() [0xac4dd000..0xac4de030] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656) - locked <0x8a6fcb28> (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:595) "http-80-Processor1462" daemon prio=1 tid=0x080f51c8 nid=0x2133 in Object.wait() [0xb112e000..0xb112efb0] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656) - locked <0x8a6fcda8> (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:595) "http-80-Processor1460" daemon prio=1 tid=0x0832e810 nid=0x2131 in Object.wait() [0xb173a000..0xb173aeb0] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656) - locked <0x8a701440> (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:595) "http-80-Processor1457" daemon prio=1 tid=0x08105d18 nid=0x212e in Object.wait() [0xabf7b000..0xabf7c130] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656) - locked <0x8a703840> (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:595) "http-80-Processor1456" daemon prio=1 tid=0x08543a10 nid=0x212d in Object.wait() [0xaf1b6000..0xaf1b70b0] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656) - locked <0x8a7038d8> (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:595) "http-80-Processor1453" daemon prio=1 tid=0x082e9aa0 nid=0x212a in Object.wait() [0xae6a..0xae6a0f30] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656) - locked <0x8a703970> (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:595) "http-80-Processor1450" daemon prio=1 tid=0x082f9ea0 nid=0x2127 in Object.wait() [0xabefb000..0xabefb1b0] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656) - locked <0x8a703a08> (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:595) "http-80-Processor1449" daemon prio=1 tid=0x08350280 nid=0x2126 in Object.wait() [0xad5ff000..0xad600130] at java.lang.Object.wait(Native Method) at java.lang.Object.wait
Re: Performance issue with Tomcat 5.0
One more Question :: for Tomcat config file these are default settings :: maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="2" disableUploadTimeout="true" how i should set maximum values because , many times it happens client get page can not be displyed message this hapens when there is load of 700 concurrent users ,, is it due to concurrency ? what should be accept count ?? or those theads ? i am using linux machines for server how to go for those configurations ? please suggest , -- View this message in context: http://www.nabble.com/Performance-issue-with-Tomcat-5.0-t1442675.html#a3897750 Sent from the Tomcat - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Java process segfaulting and using 100% CPU
Just Type kill -QUIT command you will get the thread dump in catalina.out file of tomcat log folder u can identify the ur thread which are culprit from that -- View this message in context: http://www.nabble.com/Java-process-segfaulting-and-using-100-CPU-t1474571.html#a4001573 Sent from the Tomcat - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.24 - Out of memory
just increase your max memory of JVM , problem will get solved -- View this message in context: http://www.nabble.com/Tomcat-4.1.24---Out-of-memory-t1509167.html#a4098698 Sent from the Tomcat - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat Manager
action [ *.do ] Processing time: 17146.393 s Max time: 79823 ms Request count: 2469 In My application tomcat used as web server & Jboss as AS What is mean by Max time ? IS it the Max time taken by any do request or what ? Please comment -- View this message in context: http://www.nabble.com/Tomcat-Manager-t1754215.html#a4769623 Sent from the Tomcat - User forum at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
