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) A deadlock is multiple processes wait for releasing locks on resources each other, and finally stop their processing.

b) For avoiding deadlocks, it is important to conduct not only unit testing but also integration testing. Parallel testing, which several users access to application codes, modules, or database records concurrently, is also effective.

c) A good class, good atmosphere and we learn something new all the time.

d) going too fast, your voice should be increased.