In this post, I want to elaborate on one more common mistake. Well, mistake may be too strong word. It's about a default option when you run a Java JDK installer (see the other post for more on JDK vs JRE options).
In short, I make the case here for why you should NOT let the JDK installer implement its "public jre" option.
Many find after applying a ColdFusion update that either CF won't start at all, or they can't access the ColdFusion Admin, or some part of CF or their app doesn't work. The problem may be simply that there was an error in the update process CF did, and it may be rather easily confirmed and resolved.
In this post, I share several tips and observations to help resolve this, based on my years of providing remote CF troubleshooting support.
The TLDR version: check the ColdFusion update log (not logs in the normal CF "logs" folder. More detail below.) And if there are errors, try stopping CF yourself and then either try the update again, or if it still fails, try to manually apply the update from the command line. If that's enough to get you going, great--especially if you ARE in panic mode! (If the "problem" you need to solve, instead, is that you can't get CF to show you updates because you're behind a firewall preventing outbound internet access, I help with that also, toward the end.)
For most people, though, even those "simple things to do" can prove challenging (and understandably so). And you may find different resources on the web offering perhaps truncated discussions of the topics, which is why I elaborate on things in this post.
And even if you're in a panic, it may take only about 10 minutes to read this whole post. (You can also hire me to help instead, of course. See the link above.) Hope the info to follow is helpful for you.
(There was some challenge in getting all the speakers posted until just last week, so though I had known I was speaking for months, I held off announcing it until I could point to the link.)
I'll be presenting (as I do for each release) my "Hidden Gems In ColdFusion 2016" See the description via the links above. It should be as classically useful as ever, whether for those either new to or experienced with CF 2016.
I certainly do appreciate the conference team selecting me again to be a speaker. I've spoken at each of the 3 so far, the first in 2013.
The conference is always a great time (and has gotten larger and better each year, by most accounts). And Vegas is of course a great location (though honestly I barely leave the venue the whole time). Then there are all the great attendees, and sponsor booths, as well as nearly the entire CF team on hand, and of course lots of useful information shared from all the presenters.
If you'll be attending, I hope to see you there! And if you're still considering it, see the Why attend? page and other links offered there. Finally, note that the "early bird" price has been extended to August 31. See the Pricing page.
You can find them listed as "whitepapers" at the bottom of ColdFusion.com (as I view it today, at least), so keep an eye there to see if perhaps any others may ever be added.
Here are the docs, with some observations also about their size and version, if available:
- Lockdown Guide (85 pages, currently version 1.0, released Feb 2) - An update to the classic document that Pete Freitag has been doing for CF for a few releases. Everyone should read this, and heed its recommendations. I'll have more to say on that in another post.
- Migration Guide (22 pages, currently version 2.0, no date offered) - Focuses on a few things: how installation on a current server running CF already offers to migrate admin settings; how one can do that with the CF Archive (CAR) feature (available for CF Standard since CF11); using the Code Analyzer, and how to troubleshoot some server-level migration issues. For more on "what's new" in 2016, see the docs page on What's New in CF2016. For more on what's deprecated, see the docs or my other post discussing what's deprecated in 2016
- Server Performance White Paper (9 pages, version 2.0, no version or date info offered) - Discusses specific performance improvements in CF 2016 (not performance of CF in general, nor performance-related changes in previous releases, nor all available optimizations in code or config). It's focused solely on changes in CF 2016 (or could be a huge document), whether regarding existing code/configuration as migrated or as impacted via new config/coding options available. Includes an appendix indicating the server and CF admin configuration for the testing they did.
- API Manager Performance White Paper (18 pages, no version or date info offered) - Discusses load testing done against the new API Manager, and the rate of traffic sustained (very important as an aspect of the API Manager is to act as a gateway for performing, managing, monitoring, caching, and even throttling API calls, whether against CF or any server in your infrastructure). Since the API Manager is a new product, it's a larger document than that on CF, focused as it is only on changes in 2016 (in case anyone may comment that the CF Performance guide is only half its size)
There is also now a single page from Adobe listing all the CF2016 whitepapers (and datasheets).
Hope that's helpful. Check 'em out.
Have you heard of the new "metrics log" option that was enabled in CF10? If you have not, it's worth knowing about (there's precious little documentation, and I'll point to it, and give you still more info to help you use it). It's a useful, low-impact mechanism to get some high-level metrics logged by CF every 60 seconds (by default), and stored along with other CF logs.
If you did know about it, you've probably had some problems with it. Why does it show "nulls"? What do reported metrics really mean? Why do they not jive with what I'd expect to be the numbers reported?
In this post, and a Part 2 to come, I will introduce the metrics log, pointing out some key things you need to know to have it setup to work at all, and then I'll share my observations of things I've come to understand about the reported metrics.
Fortunately, the list is pretty short:
- The ColdFusion API Manager (for more, see this summary and still more details)
- The Security Analyzer (called from within ColdFusion Builder, but works only against CF Enterprise...and not even CF Developer edition). More in the docs
Before any chime in to complain about the fact that these features are Enterprise-only (and that the Security Analyzer is not even supported against the free Developer edition), I do agree with you. These were both quite surprising to most paying close attention. (There's even a more subtle limitation regarding the Security Analyzer: it only works against an Enterprise CF deployment if that deployment is running with the "Developer profile", not either the "Secure" or "Production" profiles.)
Update: See my comment below about how you can use an Enterprise license key on a dev/test server, to allow you to use the Analyzer on other than your production server. An Adobe representative confirmed my observation today on the Adobe webinar reviewing CF 2016 (recording to be posted there soon, if not by the time you read this.)
FWIW, if you would like to find a more substantial comparison of the differences between CF Enterprise and Standard (including all the differences that are NOT new to CF2016), see this Buying Guide table from Adobe.
Before we proceed, let me note: if you're already aware of pricing, and want to complain about it, or want to know about anything beyond what's documented on the Adobe site (I offer several references below), this is not a place where such things will be debated.
I'm simply presenting actual pricing information that I found on the Adobe site. Only Adobe, or perhaps a reseller, can answer questions that are NOT answered on the Adobe site, as I have presented here. If you may find that helpful, please read on. If you were thinking this was going to be a place discussing the FACT that Adobe charged for CF, or how much, etc., that's NOT the goal here. Sorry.
In the past, I've tracked these Admin changes in each release, in the various "Hidden Gems" talks I've done about each release. (Somehow I never did a blog post about those earlier releases, at least 9, 10, and 11. The last such post I did was about Admin changes in CF8.)
So without further ado, here are the changes I've found.