tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Caldarale, Charles R" <Chuck.Caldar...@unisys.com>
Subject RE: Tomcat 5.5.23 keeps starting threads until OS runs out of memory
Date Tue, 14 Jul 2009 01:59:36 GMT
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Subject: Re: Tomcat 5.5.23 keeps starting threads until OS runs out of
> memory
> 
> I'm surprised you're not hitting a thread maximum in the OS
> and halting the JVM.

I'm not aware of any hard limit in Windows; regardless, hitting such a limit just returns
an error status on the system call, not a process abort.

> Showing more of the stack trace will certainly help reveal the problem.

Not likely; that will only show the stack of the started thread, not where it was started
from.  A heap profiler should show who created the Thread objects, if the profiler captures
enough of the call stack at object creation time.

One would think a grep of the webapp source for calls to start() would be a rather quick first
cut if a profiler can't be used.
 
If the source isn't available, then one possible way to trap the origin of the Thread.start()
call is to enable a security manager and only allow start() calls from Tomcat, not webapp,
code.  This would probably require several iterations and would be somewhat tedious.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus
for use only by the intended recipient. If you received this in error, please contact the
sender and delete the e-mail and its attachments from all computers.

Mime
View raw message