Jason Britton wrote:
So while working on reproducing tomcat webapp hang as earlier discussed, a
different tomcat serving up a single webapp on same box also stopped
responding, jvm for this tomcat is still running but when trying to reach it
via browser I get error page of unable to connect.
Thread dumps for both problem tomcats seem to exhibit same core problem, at
least in my analysis. I would really appreciate your feedback on my
analysis of the situation and things anyone thinks I may be over looking.
Well, here's an oversight: The threads below show concurrent execution
of a prepared statement. The fact that a thread own the lock, is buried
well into executing that statement, and is waiting for a read from a
socket doesn't mean it's an issue with the AJP - it could well be a DB
locking problem.
You need to examine the Oracle side of things in parallel and start
looking at database lock contention. I don't know the semantics of
Oracle's JDBC driver when managing a prepared statement - especially if
it's done concurrently, so I can't give you any trails to follow...
I'd focus on forcing the thread holding the lock to abort on the Oracle
side of things - if it frees up the other threads, you have a new point
to start diagnosing...
-- D Mansfield
On both tomcat jvms when they get to the point of locking up, thread dumps
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
