Alexey,
Thanks for taking the time to reply. I'll try all your suggestions
but I wanted to investigate the windows vs linux possibilities. Does
the fact that this Tomcat behavior does not occur on the windows-based
development server offer any clue as to what may be happening on the
From: Wm.A.Stafford [mailto:[EMAIL PROTECTED]
Does
the fact that this Tomcat behavior does not occur on the
windows-based
development server offer any clue as to what may be happening on the
linux server when Tomcat hangs?
I'm going to take a guess: server load. How heavily do you
Peter,
Thanks for replying. I don't think server load is a factor but I
will look into it. What makes me think that load is probably not the
cause is that when there are no startup errors everything starts and
runs as normal in the normal amount of time. The problem occurs when
one
Everything is possible, but unlikely. Please try running server stack
trace from
http://tmitevski.users.mcs2.netarray.com/stacktrace/app/launch.jnlp to
get a thread dump. It will show the list of threads and what locks they
have acquired and what locks they are waiting for.
- Alexey.
Thanks Alexey. Unfortunately, the server in question is not ours and we
do not even have log in on it, so any kind of sane analysis is probably
out of the question.
All we can do is try deploying another version with changes that will
either fix the problem (we hope) or yield some more
There can be a simple problem with locking - see
http://tomcat.apache.org/faq/windows.html#lock . On Linux the files are
usually not locked, so you can get class not found exception when a
jar file is replaced with a new one.
Ask administrators to get the stack trace (and check if CPU is at
