portal entry | What iT iS dESign studios

Title:

ColdFusion Debugging on Production

August 31, 2018 05:18:54 PM GMT

5 Comments

<p>Today’s short note is brought to you by “Don’t Do That On Production!” At CF Webtools often times we get called in to help troubleshoot servers that are failing to perform well. We often hear the same sort of symptoms that goes like this. The server has been running fine for months then suddenly for no reason it’s slow, CPU usage is high, and it hangs or crashes multiple times per day. This always prompts us to ask the same […]</p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2018/08/coldfusion-debugging-on-production/">ColdFusion Debugging on Production</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>

Labels: Blog, ColdFusion

Comments:

Always a good reminder for folks. Thanks, guys.

Comment by Charlie Arehart

1234 | September 02, 2018 11:54:44 AM GMT

Thanks For the article. Never thought that enbaling Debugging will cause performance issue. 
I always thought that debugger will run only if there is an error.

Comment by Tushar Bhaware

1247 | September 03, 2018 05:59:19 AM GMT

Hi Wil and Charlie,

IMHO, the "Debugging IP Addresses" feature should IP-restrict the _generation_ of debug output (not just the display of it).

Adobe can/should this be 'fixed'? Something I'm missing?

Thanks!,
-Aaron

Comment by Aaron Neff

1238 | September 06, 2018 08:08:41 AM GMT

Yes, I would agree it should (only generate and show debug info for listed ips).

I've seen situations where it did and did not, over the years. Not sure of when it has and has not worked as we would expect, and what may affect that if anything.

Another variation is whether it should generate when cfsetting showdebugoutput is enabled. That's less obvious, as it does say only don't "show" it, but see https://tracker.adobe.com/#/view/CF-4201076 where recently I was working with a client who experienced an impact in that situation.

That said, note that he reported ONLY seeing the impact for a request from an ip in the debugging list. 

Curiouser and curiouser.

Comment by Charlie Arehart

1239 | September 06, 2018 11:40:08 AM GMT

Hi Charlie,

FWIW, IMO, cfsetting(showdebugoutput=true) shouldn't allow the generation of debug output if 1) "Enable Request Debugging Output" is disabled or if 2) "Debugging IP Addresses" is populated but doesn't contain the user's IP.

And, conversely, IMO, cfsetting(showdebugoutput=false) shouldn't prevent the generation of debug output if 1) "Enable Request Debugging Output" is enabled and 2) "Debugging IP Addresses" is empty or contains the user's IP.

Thanks!,
-Aaron

Comment by Aaron Neff

1244 | September 11, 2018 09:46:17 AM GMT