There is only 1 JDBCProbe thread in the thread dump and no other threads are executing checkTime We didn't change to DijkstraSemaphore.
Actually this code is not blocking by itself, but the oracle driver does. When the Statement object tries to retrieve data from oracle through the connection object the connection object is locked by the close() call. And the connection close call is waiting for the Statement object to stop retrieving and close. This maybe is oracle specific, but this could also be the case for more drivers. It looks like it that it is better now. Nico Klasens -----Original Message----- From: Kees Jongenburger [mailto:kees.jongenburger@;omroep.nl] Sent: Thursday, November 14, 2002 8:52 PM To: [EMAIL PROTECTED] Subject: Re: deadlock on JDBCProbe and MMobjectBuilder On Thursday 14 November 2002 07:32 am, [EMAIL PROTECTED] wrote: > Our query is returning in 20 milliseconds. So that is not the problem. > > Well the problem is still there in the newest MultiPool. The nowTime > variable in the checkTime method should be inside the synchronized block. > We think, we created a situation where the thread was waiting for a lock > for longer than 120 sec. > We are testing now if this is the solution. did you also update the DijkstraSemaphore? > > Nico Klasens
