Community
Participate
Working Groups
I opened the new integration build for 11/18/03 on a new workspace and started taking files from CVS. Afterwards, I was looking at my error log and came across an error that said, "Deadlock detected. All locks owned by thread Worker-6 will be suspended." Just thought I would let you guys know :) (Stack trace below) java.lang.IllegalStateException at org.eclipse.core.internal.jobs.DeadlockDetector.reportDeadlock (DeadlockDetector.java:388) at org.eclipse.core.internal.jobs.LockManager.addLockWaitThread (LockManager.java:100) at org.eclipse.core.internal.jobs.OrderedLock.doAcquire(OrderedLock.java:151) at org.eclipse.core.internal.jobs.OrderedLock.acquire(OrderedLock.java:98) at org.eclipse.core.internal.jobs.OrderedLock.acquire(OrderedLock.java:74) at org.eclipse.core.internal.resources.WorkManager.checkIn (WorkManager.java:109) at org.eclipse.core.internal.resources.Workspace.prepareOperation (Workspace.java:1516) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1549) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1579) at org.eclipse.team.internal.ccvs.core.util.SyncFileWriter.createCVSSubdirectory (SyncFileWriter.java:378) at org.eclipse.team.internal.ccvs.core.util.SyncFileWriter.writeFolderSync (SyncFileWriter.java:196) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.commitCache (EclipseSynchronizer.java:906) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer$1.run (EclipseSynchronizer.java:521) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1554) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1579) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.flush (EclipseSynchronizer.java:519) at org.eclipse.team.internal.ccvs.core.syncinfo.ReentrantLock$ThreadInfo.flush (ReentrantLock.java:179) at org.eclipse.team.internal.ccvs.core.syncinfo.ReentrantLock$ThreadInfo.popRule (ReentrantLock.java:105) at org.eclipse.team.internal.ccvs.core.syncinfo.ReentrantLock.release (ReentrantLock.java:289) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.endBatching (EclipseSynchronizer.java:505) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.run (EclipseSynchronizer.java:1383) at org.eclipse.team.internal.ccvs.ui.operations.CheckoutProjectOperation.checkout (CheckoutProjectOperation.java:153) at org.eclipse.team.internal.ccvs.ui.operations.CheckoutMultipleProjectsOperation. checkout(CheckoutMultipleProjectsOperation.java:52) at org.eclipse.team.internal.ccvs.ui.operations.CheckoutOperation.checkout (CheckoutOperation.java:46) at org.eclipse.team.internal.ccvs.ui.operations.CheckoutOperation.execute (CheckoutOperation.java:31) at org.eclipse.team.internal.ccvs.ui.operations.CVSOperation.run (CVSOperation.java:128) at org.eclipse.team.internal.ccvs.ui.operations.CVSNonblockingRunnableContext.run (CVSNonblockingRunnableContext.java:47) at org.eclipse.team.internal.ccvs.ui.operations.CVSNonblockingRunnableContext$2.ru nInWorkspace(CVSNonblockingRunnableContext.java:67) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run (InternalWorkspaceJob.java:37) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:62)
This thread looks OK to me (i.e. we obtain our locks in the proper order). There may be another thread that violated the lock ordering. Moving to Core. Would it be possible to get the trace of all threads involved in the deadlock?
Unfortunately that was the only trace I had in my log pertaining to this deadlock event :( Sorry!
Sorry, my last question was a question to Platform Core and not to the reporter of the bug. I was asking if it was possible to have the Job mechanism write the traces for all threads involved in the deadlock to the log and not just the one that Core decides to terminate (since that thread may be innocent)
*** This bug has been marked as a duplicate of 46894 ***
