a Describe an application that can deadlock or starve a thre

a) Describe an application that can deadlock, or starve a thread.

(b) Describe a testing strategy that would detect such a problem efficiently.

(c) Tell us what you liked about this class.

(d) Tell us what you did not like about this class.

Solution

A).

The application go into deadlock condition if

1. Hold and Wait in which the application should hold a reserve and wait for other reserve

2. No Preemption in which the application only release the resource willingly

3. Circular Wait in which the application to come for a resource held through another

4. Mutual Exclusion in which the application claim exclusive control of resources the application needs

B).

A testing approach include the not only unit testing but also integration testing. Separately from this

To test the deadlock locks the subsystem to detect and tale them and heavy handed approach like using

Java Path Fidner

C).

Deadlock detection is actually essential in systems where similar transactions are working and is also use to increase the competence and the fault tolerance of the Distributed System

D).

It depends on the student whether the class is liked or not.