In these programs, JCheck provides the more sophisticated UI, while Threadalyzer provided a concrete diagnosis of a race condition. I found these programs, however, to be less compelling in terms of delivering value. From neither did I learn anything fundamental about the behavior of the program that could lead me to improve its efficiency. The argument for either of these two programs is that, if they deliver the goods even once, which is to say if they diagnose an elusive multithreaded bug, they're worth the money. In the end, such a usage profile argues for DevPartner's less innovative, familiar interface over JProbe's more ambitious, but somewhat confusing interface.
Innovative interface shows great potential.
Good information displays. Interface usability needs refinement. Occasional display problems. Thread debugger not as innovative as profiler. Easy to use.