portal entry

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

Preview builds of ColdFusion (2018 release) Update 6 and ColdFusion (2016 release) Update 13 released

| View in Portal
November 13, 2019 11:25:24 AM GMT
<p>UPDATE: 11/20/2019: We’ve released update 4 of CF 2018 and update 13 of CF 2016. For more information, see Update blog. IMPORTANT: These are preview builds and we DO NOT recommend applying them to your production environment. We are pleased to announce that we have preview builds available for the following updates: ColdFusion (2018 release) Update 6 ColdFusion (2016 release) Update 13 The preview updates contain fixes for bugs that were reported after the release of the previous updates. We […]</p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2019/11/preview-builds-coldfusion-2018-release-update-6-and-coldfusion-2016-release-update-13-released/">Preview builds of ColdFusion (2018 release) Update 6 and ColdFusion (2016 release) Update 13 released</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>
Labels: Adobe ColdFusion, Adobe ColdFusion 2016, Adobe ColdFusion 2018, Blog, coldfusion 2016 update 13 pre-release, coldfusion 2018 update 6 pre-release, coldfusion pre-release updates, ColdFusion updates


Thanks as always, Saurav. But I'd add two points for the sake of readers: <ul> <li>I don't see mention here that folks should upgrade their web connectors. Since the update includes a connector fix, isn't it true that that fix won't take effect without affected folks intentionally applying the connector upgrade, via the upgrade feature of the wsconfig tool? I have posted today <a href="https://www.carehart.org/blog/client/index.cfm/2019/11/13/when_how_update_cf_web_connector/" rel="nofollow">a blog post about that wsconfig UI upgrade button</a>, for those who may have missed it.</li> <li>Second, I want to reiterate (and make sure folks using this preview build note) the critical importance of his final comment--that if you change the cf admin to point to this new url for the preview build, you must then change that url back to the original one (using the button offered in the admin), so that you'll know about and can obtain future updates.</li> </ul> Here's hoping this update does resolve all the problems introduced in the Sept updates. Speaking of that, I'll make one more plea for my proposal that Adobe offer an option for folks to get only security updates initially (if they want), via a 2-update approach, where one of the updates has <em>only the latest security updates</em> (and any bug fixes/new features from the previous update), thus allowing interested folks to defer anything but security updates to that next update. See my post for more, and the tracker feature request to add votes to: https://www.carehart.org/blog/client/index.cfm/2019/9/26/proposal_for_new_cf_update_process
Comment by Charlie Arehart
3531 | November 13, 2019 01:18:48 PM GMT
Thank you, Charlie, as always. We'll make the changes you'd suggested.
Comment by SauravGhosh
3530 | November 13, 2019 02:13:40 PM GMT
Can we try this again?  What am I doing wrong? When following the above instructions for upgrading 2016 using the Administrator, I receve a CFWindow with a pop-up with a broken image ("../images/error_icon 24x24.png")  that states: <blockquote>Error occurred while downloading the update: For input string: ""</blockquote>  
Comment by James Moberg
3529 | November 13, 2019 02:48:19 PM GMT
James, please confirm you put in the correct url offered above. You may want to visit it also in a browser on the cf server to be updated. It should return an xml feed, as it does for me. That's what cf would then receive and process when you hit the "check for updates" button. And was your error from when you clicked that check for updates, or the download, or the download/install button?
Comment by Charlie Arehart
3528 | November 13, 2019 03:19:06 PM GMT
I entered the correct URL.  I copied & pasted it directly from this blog post.  The information is also displayed in the screen shot. If the URL was wrong, you'd think that the information displayed wouldn't be correct. This blog may have truncated my uploaded image. (When I click the image, I only see the thumbnail square.)  Here's the same screenshot in a separate Twitter post: <a href="https://twitter.com/gamesover/status/1194630667016867846" rel="nofollow">https://twitter.com/gamesover/status/1194630667016867846</a> NOTE:  I always click "download" first and then click "install" after the download has successfully completed.
Comment by James Moberg
3527 | November 13, 2019 03:38:53 PM GMT
<strong>QUESTION:</strong>  Am I being moderated or something?  I don't see my responses immediately after I submit them.  It makes me think that something is either broken or I submitted something that requires special approval.
Comment by James Moberg
3526 | November 13, 2019 03:41:37 PM GMT
James, everyone's comments are indeed moderated. It's frustrating, as it can mean we don't see them appear for hours, and by then there may be cross-chatter from folks where the context is lost by the time all comments appear. Or people post comments over and over thinking they made a mistake. Grr. Adobe had said they were working on it, to resolve or improve things. Hasn't happened yet.
Comment by Charlie Arehart
3525 | November 13, 2019 08:25:23 PM GMT
James, can you pls. share the errors reported in the browser debugger when you try the workflow. Also can you pls check the CF log for any errors corresponding to your wolrflow (exception.log and coldfusion-out.log if you are on a standalone installation of CF)
Comment by PiyushN
3524 | November 14, 2019 05:23:00 AM GMT
Thanks for the clarifications, James. I'll report that I can confirm getting and running the preview on CF2016(if you wondered if anyone had been able to). And separate from what Piyush has helpfully offered, here's something you may want to consider in the meantime: what's the  MD5 checksum for the jar file you got (hotfix-pr-013-316217.jar, downloaded to CF's cfusion hf-updates folder)? Mine was e017547d98e9d9eb03ee20caa01247fa. And for any readers who may wonder how to easily get such an md5 checksum for a file on Windows, there's a built-in utility that I show how to use here: <a href="https://www.carehart.org/blog/client/index.cfm/2018/9/20/how_to_get_checksum_on_windows" rel="nofollow">https://www.carehart.org/blog/client/index.cfm/2018/9/20/how_to_get_checksum_on_windows</a>
Comment by Charlie Arehart
3523 | November 14, 2019 03:01:35 PM GMT
About this preview process, a couple of things are unclear, since this has so rarely happened. And I see a related opportunity for improvement: <ul> <li>if one changes the url, and forgets to "change it back to the default", they will never know that there are new updates.</li> <li>It would be helpful if the CF Admin update UI would offer an indication/warning on the "available updates" tab, telling people that they have changed from the default update URL</li> <li>And what will happen when update 13 comes out, even if people DO change the URL back to the default? Will they be told that 13 is available? and will it install over/replace the preview? Or would people need to REMOVE preview 13, to see that the new 13 was available? (And I assume if they don't change the URL back to the default, they will not know of any new updates until some future preview comes out, right? That's why the warning should be there.)</li> </ul>
Comment by Charlie Arehart
3520 | November 14, 2019 08:32:10 PM GMT
PiyushN, I noticed some 404 errors in the developer console.  Something kept trying to be anmiated using a YUI library that appears to no longer exist. /cf_scripts/scripts/ajax/yui/yahoo-dom-event/yahoo-dom-event.js /cf_scripts/scripts/ajax/yui/animation/animation-min.js While these errors appeared, the issue I was encountering wasn't due to this. NOTE:  You may want to use Chrome F12 Developer Tools to read the console errors that are thrown in the admin section. In addition, there's a CSP error & "elements w/non-unique IDs" DOM error in the Flex integration section.  
Comment by James Moberg
3534 | November 15, 2019 02:46:18 AM GMT
I chose the "Install via Administrator" route to udpate to CF2016u13. I finally logged in to the Windows server, noticed that it CF was running at 99% CPU and killed the process.  After auto-restarting, I attempted the update again and the install was successful on the first attempt.  (This is a dedicated "developer" edition server.  This has happened before and may be due to a memory leak or something. I haven't seen this with any server that is licensed and in production.) Here's a video of the strange behavior I was encountering. <a href="https://youtu.be/eM07Lpltyus" rel="nofollow">https://youtu.be/eM07Lpltyus</a> NOTE:  I'm now going to recommend restarting the CF Service prior to installing via the ColdFusion Administrator.
Comment by James Moberg
3533 | November 15, 2019 02:55:31 AM GMT
James, As Charlie and Piyush had suggested, are you still seeing the error? Could you also send the log files to <a href="mailto:saghosh@adobe.com," rel="nofollow">saghosh@adobe.com,</a> so that we can take a closer look?
Comment by SauravGhosh
3532 | November 15, 2019 05:36:24 AM GMT
James, good to know that the update installed. About CF hogging the CPU cycles, did you notice anything in the CF logs? If not, you can try capturing thread dumps of the CF process, the next time that happens. About the 404s from the YUI lib., that should be harmless... and expected as we've deprecated the JS lib... it no longer is bundled with CF.
Comment by PiyushN
3538 | November 15, 2019 06:37:28 AM GMT