Thanks for the response, there is issue with neo-datasource.xml file. One of my collegues suggested we put in a empty servicename node inside
...
<var name="DATA_SOURCE">
<struct type="coldfusion.server.ConfigMap">
<var name="urlmap">
<struct type="coldfusion.server.ConfigMap"> (Inside this node)
<var name="servicename">
<string>
</string>
</var>
....
and this resolved the issue. We just have to use CF code to insert the missing element.
I agree this is a bug (https://tracker.adobe.com/#/view/CF-4211297) I submitted it but not response yet.
Thanks for sharing this, dejank. One thing is not clear from your answer here (or in the bug report you created and your first comment there offering this workaround), and I want to offer it for future readers. Please confirm if you agree.
Folks will find that for whatever datasource they are looking at, they will have the var name="yourdatasource" and then that first <struct type="coldfusion.server.ConfigMap"> line right inside of in, then at some point (within that) they will find the <var name="urlmap"> you mention (there may be other elements before it), and then inside of that will be yet ANOTHER configmap line (like you show), which may or may not have other elements inside of it, and it's within THAT that they should add your last 4 lines.
Of course, messing with (even just looking at) these neo*.xml files is challenging because they are not only XML (usually just one big long line) but also "wddx-formatted" XML, making it all the more clumsy. It would help to open the XML in any sort of editor or online tool that can render it into a nicely formatted hierarchical display. (In fact, those on Windows will find that using lowly Internet Explorer does a really NICE job of at least DISPLAYING XML file content in such a hierarchical way.)
You do then have to be VERY careful when editing the file, as the slightest mistake in leaving out a bracket or quote could render it unable to be processed by CF. Indeed, before one does edit the file, they should absolutely make a copy in case they mess anything up, so they can revert to where they started.
And you didn't mention it here, but of course one would need to restart CF after making any such change, for it to take effect.
Hope all that's helpful, for others who may find this and jump to your offered solution.
BTW, you (or someone) had kindly marked my one of my earlier replies as one of 3 listed "correct answers", but I have unmarked it, as it may have some value but really yours is THE answer--and BKBK did indeed point you to that indication in the error of an issue related to "servicename". Those both remain marked as "answers".