Thanks for the insight Dave. I have several threads sitting spinning on socket read at the moment and dba reports zero database locks of any kind on database they're trying to read from (a qa database). Quite baffled as to what's happening to these database connections and why every now and then thread sits on socket read while trying to read from database. Situation becomes serious and app completely dead locks when the socket read hang happens inside synchronized block.
On Fri, Oct 22, 2010 at 10:36 AM, Dave Mansfield <dmansfi...@sbcglobal.net> wrote: > > > 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 >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
