RESTful API does not work after appling Update 11 of ColdFusion 2021

[jianpingt85715541]

At the Admin interface, I was not able to register any new REST service.

Existing REST APIs do not work. Showing 500 error at weblog.

[Texas_Ranger]

We are experiencing the same thing. It looks like the latest updates (11 or 12) to CF2021, and also our dev CF2023 are suddenly adding a subfolder to the REST URL.  So we used to have something like localhost:8500/rest/v1/app, but now it is requiring us to put the subfolder, so localhost:8500/rest/v1/api/app (the app.cfc is in the api subfolder of where we have the REST service directory registered).  Does anyone know if this is a new feature or a bug?

[Texas_Ranger]

Actually, my fault, I did not update the connector when I applied update 12 because I saw it wasn't required.  Didn't even think about the fact that I skipped update 11 and it was required in that one. As soon as I updated the connector, the REST services worked as before.

[Charlie Arehart]

Glad you found that to be the solution. As for "not even thinking to update the connector", you're not alone in that oversight. It's sadly quite common--and often it does NOT matter that much (the changes may not be that signficant), but sometimes it does. Seems this is one of those.

FWIW, the technote for the updates DO always have a table at the bottom indicating which updates DO (or do NOT) call for that update, such as that for CF2021 update 12. But it's easy to not notice (and the table's column header still says "recreation required", but since CF2016 it's a simple "upgrade" button in the wsconfig UI tool).

Thanks for pointing out the issue and solution for folks. jianpingt85715541, does that solve the problem for you as well?

[Texas_Ranger]

Thanks, Charlie, as always! I'm still having the same issue in CF2023 Update 6, did all the same things and no love. On one of our servers, I had to remove the connector and re-add it, then upgrade it before it worked, but at least now we finally have it working on all the 2021 servers. Since our CF2023 isn't being used for anything other than testing so far, I can deal with 2023 now as I have time.  I might just start over and try to apply everything in order because this is just a strange issue.

[Charlie Arehart]

Glad to have helped. But speaking of order, I'll add that there should be no value in doing the connector "upgrade" rght after having just added it (at the same update level). When you add it, it's implemented with the wsconfig features that WOULD be updated if you did an upgrade. The latter is for when you have an existing connector that was added using an older version of the connector tool (wsconfig), as had been put in place by an older cf update.

In other words, updating cf updates the wsconfig tool itself, and running add or upgrade implements that new version of things in the connector created or updated. (Usually it's just a new isapi_redirect.dll for iis or mod_jk.so for apache. And that's pulled out of a folder deep within the wsconfig.jar, when the wsconfig tool is run.)

All that may be old news to some, while to others it's an interesting discovery--and to some it may be all " yadda yadda"... until someday when it won't be. 🙂

As for your cf2023 issue, it would seem it should be solved the same way. Hope you sort things out. 

[Texas_Ranger]

That's what we thought, too, but after adding it, same behavior, after upgrade, it worked. Maybe it just needed that extra restart. In any case, I'll post anything I find if I ever get the 2023 working again.  Thanks, Charlie!

Happy Thanksgiving - I'm grateful for your continued support in this community!

Walker

[Charlie Arehart]

Thanks for the kind regards.

And if you or anyone tries it (and has this question), check first on a connector "add" if the dll or so file is from sep 2023 (for these two most recent updates), and then see if it changes on a connector "upgrade". It should not (if the connector was just added).

But yep, while each action should restart the web server, if somehow it did not after the add then, sure, if it did restart after the upgrade, that could explain it. 

[jianpingt85715541 · Accepted solution]

The issue has been resolved. After applying Update 12, application.cfc is required to register REST services. The connector is optional to re-config.

Thank you all very much, especially Charlie.  I can say that the community is really helpful.

[Texas_Ranger]

That's interesting, because we tried that, too, but had the same issue.  I will try that again in CF2023. Thanks for letting us know!