| Summary: | TVT3.1.x:TCT117: What is contended monitor? | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | CDE Administration <cdeadmin> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | camle, Karice_McIntyre, kitlo, mtveety, steven.wasleski |
| Version: | 3.1.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| URL: | 117 | ||
| Whiteboard: | |||
|
Description
CDE Administration
<cde:tctdetail> Testcase: org.eclipse.jdt.debug\jdimodel_jar\org\eclipse\jdi\internal\spy\TcpIpSpyMessages.properti Project: WSW3A Component: JDT Priority: 1 Subject: What is contended monitor? Article ID: 117 Originator: oya.argun@superonline.com </cde:tctdetail> Lowering the question's severity to normal. See JVMDI spec. http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jvmdi-spec.html#GetCurrentContendedMonitor The short explanation of a contended monitor is a lock that is required by two or more threads at once - i.e. the lock is in contention because it is a single resource required by more than one consumer simaltaneously. Marking as works for me. closed |