Rolling back a hotfix

Well, yeah. (You do need to remove any jars added during a hotfix to roll it back.) Usually the technotes for each hotfix do explain this and point out as well where the jars get put (if you use the Admin interface to upload them and therefore don't know the location yourself.) It's either \lib\updates in Standard/Server deployments, or deep in an instance in the Multiserver mode of deployment (such as C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib\updates).

As for applying the hotfix causing CPU and memory problems, I would doubt that a proper implementation of a hotfix could/would cause it. I suppose a mis-implementation could (putting files in the wrong place). It's quite easy to do. For instance, people often have more than one place where the CFIDE directory may live, either in their external web server docroot, or perhaps in more than one webserver docroot, or even in the docroot for CF's built-in web server.

I have asserted that the technotes ought to be updated to tell the user to look in their CF Admin, at the Mappings page, to see where IT says the CFIDE is for that instance. Because if you update the Jars for that CF server, but then mistakenly update the CFIDE in a directory other than what CF thinks you're using, I could see there being a problem.

Similarly, I could see their being a problem if you make a mistake in updating only some files, or putting them in the wrong place even within the right CFIDE.

It's definitely unfortunate that the hotfix process (with all these manual CFIDE edits) is so easily done wrong. Before anyone chimes in to decry the situation, Adobe definitely knows and there is work underway to improve the process in the future.

/charlie