New Tomcat shuts down thread 2007-01-12 - By Christopher Schultz
Back
-- --BEGIN PGP SIGNED MESSAGE-- --
Hash: SHA1
Steve,
Steve Ingraham wrote:
> As I stated previously I manually stop and start Tomcat every morning.
> It is not that big of an inconvenience to do that in general but at the
> same time I would like to know why it is doing this and resolve it.
> There is something wrong with the application and fixing it would make
> things run smoother.
You mentioned that your users get an error when whatever happens to
Tomcat happens. Can you describe that error? I think you said something
like "not enough components". Does that appear on a stack trace, or as
an error message to the user?
I'm wondering if you are running out of database connections. (Although,
unless you require a database connection to shut down the server, it
wouldn't explain the fact that you have to kill -9 the server).
The infinite loop suggestion has a better chance of explaining /that/.
Can you wait for the server to get all messed up and take more careful
notes? That's probably the best next step to take. Check out CPU usage
(just run 'top' and see how much CPU time the java process is taking).
If the CPU isn't being eaten by java, then it's probably not a "code out
of control" problem.
Check all your log files: catalina.out, localhost_*.log,
[appname]_*.log, and any application-specific logs you may have (such as
log4j.log). These can usually be found in the TOMCAT_HOME/logs directory.
Certainly post a stack trace if you get one in any of those log files.
Another thing you can to is trigger a thread dump. From that, it's
(sometimes) possible to see that all the request handler threads are
stuck waiting on some resource. Send a QUIT (sig 3) to the application
instead of KILL (sig 9) and that should emit a thread dump (stack trace
for every live thread) to standard output (usually redirected to
catalina.out). You can inspect it yourself to see if you can detect
anything fishy, or go ahead and post it to the list and we'll see if we
can give you any advice.
The fact that a previous developer mentioned off-hand that "something
might be wrong with the memory" is not exactly encouraging, since I'm
guessing he or she didn't give you any indication of /where/ that memory
problem might be. That pretty much means that you're going to have to
start from scratch. :(
Good luck,
- -chris
-- --BEGIN PGP SIGNATURE-- --
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFp8ZH9CaO5/Lv0PARAjzCAJ43KFJuG6bza+zLGIAKygFJ97yAqACgw11n
bRAlQBGHIn6WlDZN0nzYyQg=
=T4kv
-- --END PGP SIGNATURE-- --
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
