DPJ Coverage Analysis and out of order thread synchronizations with DPJ 3.01

0 Likes

Problem:

Running an app under DevPartner Java Edition v3.X that includes code that results in a deadlock, however, when running coverage using that configuration, DPJ reports 'No out of order thread synchronizations found'

Resolution:

The reason that DevPartner Java Edition does not show any out-of-order deadlocks here is because there are never any. While it's true that all out-of-order deadlocks are deadlocks, not all deadlocks are of the out-of-order variety. Out of Order deadlocks are when monitor A is acquired, then monitor B is acquired, and then at a later time the same 2 monitors are grabbed in the REVERSE order -- B first, then A (there are several derivations of this situation and we catch them all correctly.) Also note that DPJ will spot *potential* OOO deadlocks, so you don't even have to wait until a deadlock actually occurs for DevPartner Java to catch it.

<!--- END INSERT ANSWER --->

Old KB# 11252
Comment List
Anonymous
Related Discussions
Recommended