| Eclipse Job API: Deadlock Resolution [message #277211] |
Mon, 06 December 2004 15:31  |
Eclipse User |
|
|
|
This is a multipart message in MIME format.
--=_alternative 0070B94885256F62_=
Content-Type: text/plain; charset="US-ASCII"
Hello,
Is there any way to control the way deadlocks are resolved in Eclipse Job
API. I am using OrderedLocks to acquire locks, and in case of deadlocks I
want to undo all changes done by the job causing the deadlock, and cancel
and reschedule that job.
Default Eclipse deadlock resolution releases the locks acquired by the
resolution candidate and let other jobs finish. The resolution candidate
is allowed to finish after other jobs are finished.
Maneesh
--=_alternative 0070B94885256F62_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">Hello,</font>
<br>
<br><font size=2 face="sans-serif">Is there any way to control the way
deadlocks are resolved in Eclipse Job API. I am using OrderedLocks to acquire
locks, and in case of deadlocks I want to undo all changes done by the
job causing the deadlock, and cancel and reschedule that job.</font>
<br>
<br><font size=2 face="sans-serif">Default Eclipse deadlock resolution
releases the locks acquired by the resolution candidate and let other jobs
finish. The resolution candidate is allowed to finish after other jobs
are finished.</font>
<br>
<br><font size=2 face="sans-serif">Maneesh</font>
<br>
--=_alternative 0070B94885256F62_=--
|
|
|
| Re: Eclipse Job API: Deadlock Resolution [message #277213 is a reply to message #277211] |
Mon, 06 December 2004 16:57  |
| Eclipse User |
|
|
|
Originally posted by: john.eclipsefaq.org
There are two debug .options entries that will influence deadlock
resolution:
This flag will report detailed deadlock information in the log and on
stdout:
org.eclipse.core.runtime/jobs/locks=true
This flag with throw an immediate runtime exception when deadlock occurs
(rather than trying to resolve it; useful in test suites):
org.eclipse.core.runtime/jobs/errorondeadlock=true
Note that the deadlock detection/resolution code is realy a safety net
to better handle programming errors. It is still a programming error to
introduce a deadlock, and you should not rely on automatic deadlock
resolution as part of your locking design.
--
mgoyal@ca.ibm.com wrote:
>
> Hello,
>
> Is there any way to control the way deadlocks are resolved in Eclipse
> Job API. I am using OrderedLocks to acquire locks, and in case of
> deadlocks I want to undo all changes done by the job causing the
> deadlock, and cancel and reschedule that job.
>
> Default Eclipse deadlock resolution releases the locks acquired by the
> resolution candidate and let other jobs finish. The resolution candidate
> is allowed to finish after other jobs are finished.
>
> Maneesh
|
|
|
Powered by
FUDForum. Page generated in 0.04431 seconds
Home