In the past, when doing projects, encountered on-line data source leakage and other issues are often helpless. And on the line often appear a variety of strange and strange problems, want to see the method parameters, but some method parameters do not have a log, so only through patch upgrade to solve the problem. If you encounter an emergency bug and you can't stop the service for upgrades, you're often stuck in a super-embarrassing state. A recent study of the JVM, stumbled upon a fault analysis tool, is what we are going to say next btrace. The great God can do the analysis of method parameters, the analysis of database connection pool and so on without service. It's a sharp weapon. Found a blog series on the Internet, specifically introduced the small software, so I will tidy up the link, as a small series, to facilitate the students interested in learning, while the author expressed gratitude.
One of the Btrace series: Introduction
Btrace Series II: A simple example
Btrace Series Three: A Practical case study
Btrace series four: Crack case
Btrace Series Five: the principle of realization
Fault analysis Artifact--btrace