Production Debugger

The Production Debugger for Java is a game changing “production-ready” tool to give you INSTANT insight into your production environment and MINIMIZE the time needed to identify and FIX issues

Start Free Trial   Compare Editions   See Examples    Pricing

FusionReactor Production Debugger: FusionReactor Debugger IDE

Production Debugging Highlights

Integrated Debugger

It’s all built into FusionReactor! Production Debugger gives you all the control you need to simply and securely interact with your production environment as issues unfold. The insight it provides will revolutionize how you identify problems. Unlike a typical debugger, you can setup conditional breakpoints and be alerted by email when they fire. The email will contain a link to the debug session, as well as stack trace and variable details at the instant the break point fired. It has NEVER been easier and faster to get to the root of issues.


Set breakpoints and trigger handlers

Setting Breakpoints (BP) is really easy and FusionReactor supports various methods to control breakpoints, such as On Exception, Field Modification, Java Method Entry and Source File-Line Number. You can also setup conditions which need to be met before the BP fires. The Fire Count controls how many times the BP will fire.
Other elements control how the engine will attend to the breakpoint e.g. open a debug window, email a stacktrace or capture metrics.

 


 

Pause A Single Thread

One of the options on the Production Debugger is to pause a single thread for a specific period of time when a breakpoint fires. The Debugger can control how many threads it will halt, so this ensures it doesn’t halt your whole application. In this example you can see that the thread will Timeout in 19 seconds. Unless we attend the breakpoint within that time, then the thread will simply continue to process.


Receive an Email Alert

FusionReactor can also send out an email, containing the complete stack trace PLUS all the scope variables which were set at the moment the breakpoint trigger fires.
Having the stack trace plus variables can often be enough to pinpoint what the actual issue is – so you may not even need to debug via the integrated debugger.