Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

robustExceptionEnabled doesn't seem to work in ACF2021

Description

In my `.cfconfig.json`, I have:
` "robustExceptionEnabled": true,`

This config file is definitely getting loaded, as there are several configs in there which would totally break the application if they were missing.

However, when I run into an exception, I don't see any error details or stack trace, and instead I see "Enable Robust Exception Information to provide greater detail about the source of errors".

Environment

Docker, using `ortussolutions/commandbox:adobe2021` image.

Activity

Show:

Leon Miller-OutMarch 25, 2021 at 7:10 PM

Yup. Thanks!

Brad WoodMarch 25, 2021 at 5:50 PM

Ahh, wow-- good to know. So we can close this ticket?

Leon Miller-OutMarch 25, 2021 at 3:32 PM

I figured it out. I needed to have the debugger package installed in order for robust exception reporting to work.

Leon Miller-OutMarch 25, 2021 at 2:34 PM

Hm, this is weird. My neo-debug.xml file
(/usr/local/lib/serverHome/WEB-INF/cfusion/lib) has:
```
<var name="robust_enabled">
<boolean value="true"/>
</var>
```
So I thought maybe this is some kind of secure profile issue. However, I
see this in the server startup output, so I don't think that that's the
case:
```

------------------------------

√

Setting Server Profile to [development]

 

------------------------------------------------------

 

Profile set from profile property in server.json

 

Block CF Admin disabled

 

Block Sensitive Paths enabled

 

Block Flash Remoting enabled

 

Directory Browsing enabled

 

----------------------------------------------------—
```

Brad WoodMarch 24, 2021 at 5:34 PM

It’s likely Adobe has changed where in the config file they store that flag. I’ll have to look into it. Feel free to take a peek as well if you have time. Looking at the code, it stores a boolean in a “robust_enabled” key in a struct located in the first index of an array in the neo-debug.xml file.

Won't Fix
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Affects versions

Priority

Sentry

Created March 24, 2021 at 4:32 PM
Updated March 25, 2021 at 7:19 PM
Resolved March 25, 2021 at 7:19 PM