tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torstein Nilsen" <tor_tom...@top-house.dk>
Subject RE: OutOfMemory exception explanation?
Date Tue, 27 Jan 2004 13:48:05 GMT
Hi Murat,

I'm also having some memory-leaking trouble. I'm
using HPJmeter - it's free, and can among other
stuff tell you wich objects filled the heap when
your application was terminated.

Download here:
http://www.hp.com/products1/unix/java/hpjmeter/dow
nloads/

Torstein

-----Original Message-----
From: MURAT BALKAS
[mailto:murat.balkas@rtnet.net.tr] 
Sent: 27. januar 2004 07:25
To: Tomcat Users List
Subject: RE: OutOfMemory exception explanation?






Hi,

      I need some info about these memory
profiler's. Is there any free and
easy-to-integrate-to-tomcat memory profiler?

      Thanks...

Murat



 

                      "Filip Hanik"

                      <devlists@hanik.c        To:
"Tomcat Users List"
<tomcat-user@jakarta.apache.org>

                      om>                      cc:

 
Subject:  RE: OutOfMemory exception explanation?

                      27.01.2004 01:35

                      Please respond to

                      "Tomcat Users

                      List"

 

 





download a memory profiler, should give you the
exact place where memory is
being wasted. probably in your own webapp

-----Original Message-----
From: D'Alessandro, Arthur
[mailto:Arthur.Dalessandro@cbetech.com]
Sent: Monday, January 26, 2004 11:43 AM
To: Tomcat Users List
Subject: OutOfMemory exception explanation?


We've been getting these every now and then:

Jan 23, 2004 5:03:30 PM
org.apache.tomcat.util.net.TcpWorkerThread runIt
SEVERE: Exception in acceptSocket
java.lang.OutOfMemoryError
Jan 23, 2004 5:03:30 PM
org.apache.tomcat.util.threads.ThreadPool$ControlR
unnable run
SEVERE: Caught exception executing
org.apache.tomcat.util.net.TcpWorkerThread@8a4d2e,
terminating thread
java.lang.IllegalStateException: Terminating
thread
        at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(P
oolTcpEndpoint.java:53
2)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlR
unnable.run(ThreadPool
.java:619)
        at java.lang.Thread.run(Thread.java:536)



Once this occurrs, I have to stop / start the
entire Tomcat container in
order to allow this particular webapp to function
again.  It only
effects a particular servlet mapping for a  given
webapp.  Does anyone
have any suggestions on how to resolve?  We're
running version 4.1.24..
Any leads would be great, thanks.

-Art

--------------------------------------------------
-------------------
To unsubscribe, e-mail:
tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail:
tomcat-user-help@jakarta.apache.org


--------------------------------------------------
-------------------
To unsubscribe, e-mail:
tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail:
tomcat-user-help@jakarta.apache.org





--------------------------------------------------
-------------------
To unsubscribe, e-mail:
tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail:
tomcat-user-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message