Where is the problem in my ThreadDump information?

2006-10-06 Thread Minh Tu Thanh Tran

Dear all,

Below is the Thread Dump output. I am new to this subject so that I
can not figure out what and where the problem that make Thread Dump
is. Could some one please give me some hints?

Thanks alot
Tu

Thread Dump
Output--

Full thread dump Java HotSpot(TM) Client VM (1.5.0_07-b03 mixed mode, sharing):

TP-Monitor daemon prio=1 tid=0xb0b14490 nid=0xfaa in Object.wait()
[0xb08fe000..0xb08fee40]
at java.lang.Object.wait(Native Method)
- waiting on 0x89433f70 (a
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable)
at 
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.java:559)
- locked 0x89433f70 (a
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable)
at java.lang.Thread.run(Thread.java:595)

TP-Processor4 daemon prio=1 tid=0xb0b13730 nid=0xfa9 runnable
[0xb097e000..0xb097efc0]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked 0x89438110 (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at org.apache.jk.common.ChannelSocket.accept(ChannelSocket.java:293)
at 
org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:647)
at 
org.apache.jk.common.ChannelSocket$SocketAcceptor.runIt(ChannelSocket.java:857)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)

TP-Processor3 daemon prio=1 tid=0xb0b0f6b8 nid=0xfa8 in
Object.wait() [0xb09fe000..0xb09fef40]
at java.lang.Object.wait(Native Method)
- waiting on 0x89434250 (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:474)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656)
- locked 0x89434250 (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:595)

TP-Processor2 daemon prio=1 tid=0xb0b0fec8 nid=0xfa7 in
Object.wait() [0xb0a7e000..0xb0a7f0c0]
at java.lang.Object.wait(Native Method)
- waiting on 0x894342e8 (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:474)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656)
- locked 0x894342e8 (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:595)

TP-Processor1 daemon prio=1 tid=0xb0b14978 nid=0xfa6 in
Object.wait() [0xb0afe000..0xb0aff040]
at java.lang.Object.wait(Native Method)
- waiting on 0x89434380 (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:474)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656)
- locked 0x89434380 (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Thread.run(Thread.java:595)

http-8080-Monitor prio=1 tid=0x08609b18 nid=0xfa5 in Object.wait()
[0xb0cc9000..0xb0cc91c0]
at java.lang.Object.wait(Native Method)
- waiting on 0x89378950 (a
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable)
at 
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.java:559)
- locked 0x89378950 (a
org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable)
at java.lang.Thread.run(Thread.java:595)

http-8080-Processor25 daemon prio=1 tid=0x08608ce0 nid=0xfa4
runnable [0xb0d48000..0xb0d49140]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked 0x89010c58 (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at 
org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:60)
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:407)
at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:70)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)

http-8080-Processor24 daemon prio=1 tid=0x086085f8 nid=0xfa3 in
Object.wait() [0xb0dc8000..0xb0dc8ec0]
at java.lang.Object.wait(Native Method)
- waiting on 0x89378ab8 (a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
at java.lang.Object.wait(Object.java:474)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656)
- locked 

Re: Problem: Tomcat server hang because CPU goes to 100%

2006-10-05 Thread Minh Tu Thanh Tran

Thank you very much Praveen Balaji.

Tu


On 10/4/06, Praveen Balaji [EMAIL PROTECTED] wrote:


Check how Heinz would do it:

http://www.javaspecialists.co.za/archive/newsletter.do?issue=132locale=
en_US


-Original Message-
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 04, 2006 2:56 PM
To: Tomcat Users List
Subject: Re: Problem: Tomcat server hang because CPU goes to 100%

create a thread dump (kill -QUIT pid) and look for the thread that
hangs.
then fix the bug :-)
regards
Leon

On 10/4/06, Minh Tu Thanh Tran [EMAIL PROTECTED] wrote:
  Dear friends,

 When I click on different links or button in my jsp page quickly,
normally
 everythings is ok but sometime
 the tomcat server hang, it can not response to the requests anymore
because
 the
 CPU goes to 100%

 If I publish my website, and when it may happens again the CPU goes to
 100% long enough to break down the CPU. That would be terrible.

 Does anyone know any reason that may cause the CPU runs to 100% like
this?
 Seconds, is there any java method that can take care the CPU and he
 can shut down or start up the tomcat server if needed?

 Many thanks,

 Tu

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Problem: Tomcat server hang because CPU goes to 100%

2006-10-05 Thread Minh Tu Thanh Tran

Hi Leon Rosenberg,

Do you have the sample code like what you show me? I would be much graceful
if you could send me some more code on this matter.

Thank you very much
Tu


On 10/4/06, Leon Rosenberg [EMAIL PROTECTED] wrote:


create a thread dump (kill -QUIT pid) and look for the thread that hangs.
then fix the bug :-)
regards
Leon

On 10/4/06, Minh Tu Thanh Tran [EMAIL PROTECTED] wrote:
  Dear friends,

 When I click on different links or button in my jsp page quickly,
normally
 everythings is ok but sometime
 the tomcat server hang, it can not response to the requests anymore
because
 the
 CPU goes to 100%

 If I publish my website, and when it may happens again the CPU goes to
 100% long enough to break down the CPU. That would be terrible.

 Does anyone know any reason that may cause the CPU runs to 100% like
this?
 Seconds, is there any java method that can take care the CPU and he
 can shut down or start up the tomcat server if needed?

 Many thanks,

 Tu



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Problem: Tomcat server hang because CPU goes to 100%

2006-10-04 Thread Minh Tu Thanh Tran

Dear friends,

When I click on different links or button in my jsp page quickly, normally
everythings is ok but sometime
the tomcat server hang, it can not response to the requests anymore because
the
CPU goes to 100%

If I publish my website, and when it may happens again the CPU goes to
100% long enough to break down the CPU. That would be terrible.

Does anyone know any reason that may cause the CPU runs to 100% like this?
Seconds, is there any java method that can take care the CPU and he
can shut down or start up the tomcat server if needed?

Many thanks,

Tu


My web application using tomcat server sometime make my CPU goes to 100%

2006-10-02 Thread Minh Tu Thanh Tran

Dear friends,

Sometime, when I click on different link in my jsp page quickly, then
the tomcat server can not response to the requests anymore because the
CPU goes to 100%.

If I publish my website, and when it may happens again the CPU goes to
100% long enough to break down the CPU. That would be terrible.

Does anyone know any reason that may cause the CPU runs to 100% like this?
Seconds, is there any java method that can take care the CPU and he
can shut down or start up the tomcat server if needed?

Many thanks,

Tu

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Problem with java.library.path

2006-08-07 Thread Minh Tu Thanh Tran

Thanks David,

Again, I want to start the prolog engine, so I need to load the
library of prolog when I start Tomcat 5.5.17. I think the command line
is: java -Djava.library.path=$PLLIBDIR $1
But I do not know where to put this command line in Tomcat in order to
load the prolog library when Tomcat starts. I am using Linux.

This is the error I get when using jpl methods to call prolog, just
because the prolog engine is not yet started.

Caused by: java.lang.UnsatisfiedLinkError: no jpl in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682)
at java.lang.Runtime.loadLibrary0(Runtime.java:822)
at java.lang.System.loadLibrary(System.java:992)
at jpl.fli.Prolog.clinit(Prolog.java:81)
at jpl.Query.open(Query.java:302)
at jpl.Util.textToTerm(Util.java:162)
at jpl.Query.init(Query.java:209)
at 
nats.incom.jsp.beans.predicate.PredicateBean.setExercise(PredicateBean.java:37)

Many thanks,

Tu


On 8/7/06, David Smith [EMAIL PROTECTED] wrote:

Your log message sited below is not related to accessing jpl.jar.  It's
just a message stating it couldn't use the new native APR connector and
is falling back to the traditional Coyote connector.

As far as an external jar file, best practice is include it in your
webapp in WEB-INF/lib.  In $CATALINA_HOME/shared/lib if you are using it
accross multiple webapps.

--David

Minh Tu Thanh Tran wrote:

 Hi,

 I want to use methods of an external library (jpl.jar file) inside a
 java Bean class. But I got this error message from Tomcat 5.5.17 log
 file:

 Aug 7, 2006 1:14:44 PM org.apache.catalina.core.AprLifecycleListener
 lifecycleEvent
 INFO: The Apache Tomcat Native library which allows optimal
 performance in production environments was not found on the
 java.library.path:

/usr/lib/j2sdk1.5-sun/jre/lib/i386/client:/usr/lib/j2sdk1.5-sun/jre/lib/i386:/usr/lib/j2sdk1.5-sun/jre/../lib/i386


 My question is how to solve this problem?

 Many thanks,

 Tu

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]