What I was thinking about is something like
Thread 1: lock resource A (Resource can be a certain row in the database) Thread 2: lock resource B Thread 2: lock resource A -> Waiting for Thread 1 Thread 1: lock resource B -> Waiting for Thread 2 --> Deadlock If you kill tomcat all lock are released and everything is OK from the database side. If you don't have the Enterprise Manager have a look at the documentation of the system tables and/or stored procedures, as far as I remember it's possible to query this kind of information from tables or stored procedures. > -----Ursprüngliche Nachricht----- > Von: TEOH KANG YIH [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 3. Juli 2002 09:11 > An: Tomcat Users List > Betreff: Re: TomCat 3.2.3 not respond suddenly. > > Reply: The thing that I do not understand is why do you think > it could be a deadlock in DB because I just restart TomCat but > not Oracle, the TomCat can talk to Oracle (test from login > screen where it actually reads table from Oracle)? > <snip/> > > Reply: Oracle console - if you are saying Oracle Enterprise Manager, > actually it is not implemented. Any other alternative? > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
