I have used Chronon for several weeks during a very strange project. The project was about integrating a highly complex financial system in our own infrastructure. The challenging part about this financial system was that it was written in a multitude of languages (Java, Perl, C, C++, ...) and that it had to communicate with external services and it had hard timeouts built in which were enforced externally. So if something went wrong and I wanted to find out I had only 20 seconds in the debugger to find out because then the timeouts would kick in and there was nothing I could do about it. With Chronon I was able to step through the code after it had already run with no time constraints. Saved me weeks...

Chronon is also useful to find all thrown exceptions - even the ones who are catched properly.

I am not an employee of Chronon Systems and I only used their tool once but it helped a lot.

Unlike Chronon, Takipi is built for monitoring your JVM in production, imposing minimal and predictable overhead.

Chronon is also built for monitoring your JVM in production. At least that is what they say on their website:

http://chrononsystems.com/solutions/production