tracker issue : CF-3735324

select a category, or use search below
(searches all categories and all time range)
Title:

CFAdmin won't start if CF config files are corrupted

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/NotWorthEffort

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)

Created: 04/02/2014

Components: Administrator

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: PublicBeta /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Platforms All

Vote Count: 0

I introduced something CF didn't like into my neo-datasource.xml file (NB: it was still valid XML / WDDX, but CF didn't like some of the whitespace I put in it, or something), and as a result CFAdmin simply errored.

It needs better errortrapping than this. I can understand in this situation the Datasources tab might say "service unavailable", but the rest of the admin UI should still work.

-- 
Adam

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3735324

External Customer Info:
External Company:  
External Customer Name: Adam Cameron.
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

Point taken. We might not have the time to fix it for this release but we can consider this for the next release
Comment by Vamseekrishna N.
12892 | April 05, 2014 03:22:05 AM GMT
Meddling with the xml files and corrupting it is not a normal scenario. Not worth the effort.
Comment by Rupesh K.
12893 | November 13, 2014 04:07:35 AM GMT
You're missing my point, Rupesh. I'm not quite sure *how* you missed my point, because it's there in the first sentence of the ticket, which I guess for some reason you didn't think you needed to read to understand the ticket, before commenting on it. Hint, I find it handy to use this process: * read text * understand text * then make observations about text Don't skip to the third step. That won't work. Anyway, to reiterate: I *didn't* corrupt it. It was still legit XML, and the schema was still correct. Basically (from memory, casting my mind back the seven months since I raised this), I just used an XML formatter to de-minify it so I could actually read it (rememebr the whole idea with XML is that both humans and machines can read it). It seems to me like whatever you do to read the values from it is a bit fragile, and can only cope with the file in a minified state? I agree it's an edge-case, but I'm more worried about something like *indentation* completely breaking the Admin. It should deal with it more gracefully than that.
Comment by External U.
12894 | November 13, 2014 04:24:52 AM GMT
I know the xml file without indentation in a minified state can be a pain to read. However, Indentation is not an issue at all. We keep doing that and that does not break the server or admin. It must be some issue with the xml which we can figure out only by looking at the exception stack trace during the server startup.
Comment by Rupesh K.
12895 | November 13, 2014 05:18:06 AM GMT
I will try to replicate. In the mean time, I think the status of this ticket is more along the lines of "need info" not "closed".
Comment by External U.
12896 | November 13, 2014 05:20:44 AM GMT