Automated Root Cause Analysis for ColdFusion

Thanks! Share it with your friends!

You disliked this video. Thanks for the feedback!

Added by intercd
3 Views
In this video, we are going to talk about the Event Snapshot
An automated root cause analysis tool available in FusionReactor ultimate and developer editions.

Due to a limitation in the way that ColdFusion handles exceptions and the potential to cause performance degradation
Snapshots in ColdFusion use a specific mechanism to collect the stack frames and variables when errors occur without side effects.

While you will see mostly the same information as for Event Snapshots in Lucee and other Java-based Application Servers
You will only be able to view the local variable scope on the top stack frame.

A snapshot is generated if the same error occurs twice and is stored on disk so that information is persisted between restarts.

Within my FusionReactor instance, I have a function that is failing sporadically.

By going to the Event Snapshot history you can see all requests with an attached snapshot.

To view the snapshot, you can click the hyperlink, or view the request details than move to the event snapshot tab.

In the snapshot, you will first see the error that occurred and the source file and line number for the error.

In this case, the error was a divide by zero in the function newRandom.
The erroring line is highlighted in green.

If you wish to debug the error, you can click on the left margin and configure a breakpoint.

Within the frames, the top CFM or CFC frame will contain the variables.

Other frames will be greyed out meaning no variables are available for them.

For the frame with variables, you will see the local scopes including the variables, cookies and request scopes available in the CFM request

From the Snapshot, we can see that the error in our case is caused by the fact that the int2 variable can at random be zero and cause the exception.
Changing the minimum random value to 1 would stop this issue from reoccurring.
Category
News

Post your comment

Comments

Be the first to comment