[Looking for Charlie's main web site?]

Some recently added (and evolving) documentation of the CF Admin API

You may be aware of the CF Administrator API, a way to implement most CF Administrator features programmatically, by way of a set of CFCs implemented within CF (as introduced in CF7). But have you ever wished for some complete online documentation of the many (18) Admin API CFCs, including their methods and arguments?

If so, I have some very good news--and some not-so-good news. (Some may know that you can find this info also by running the CFC Explorer--more on that in a moment.) The unfortunate news is that it's not yet COMPLETELY documented, but it's still a good start.

[....Continue Reading....]

Why you should think twice about leaving on the "public JRE" option of the Java JDK installer

This is a follow-up to a post I did in late 2014, CF911: 'Help! I've updated the JVM which ColdFusion uses, and now it won't start!'. In that post, I listed about a dozen common problems that befall people who try to update the JVM that CF is using (and it and this post apply as well to Lucee or BlueDragon, or indeed any Java application server).

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.

[....Continue Reading....]

How to solve common problems with applying ColdFusion updates (in 10 and above)

While ColdFusion 10 and later releases add a new automated update installation mechanism, what do you do if the update doesn't work? The answer may be simple on the surface, but not obvious to most. (And you'll likely be in panic mode.)

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.

[....Continue Reading....]

New whitepapers from Adobe on ColdFusion 2016: lockdown, migration, and performance

Continuing my series of posts on new things in CF2016 which some may miss,there are some new resources from Adobe about CF 2016, posted in recent days. (I suppose we may see a post from Adobe on their blog at some point, but I wanted to share it in the meantime.)

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.

ColdFusion 2016: Changes in the CF Administrator

As folks continue to explore ColdFusion (2016 Release), aka CF2016, regarding what's new or changed, I thought I'd put together a listing of what has changed in the CF Admin specifically. This is another in a series of posts I started last week on CF2016.

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.

[....Continue Reading....]

CF2016: What's deprecated and/or 'no longer supported' (note: nothing 'removed')

Continuing a series of posts I started last week on ColdFusion (2016 Release), aka CF 2016, I'd like to highlight the items that Adobe has chosen to deprecate and/or declare as "no longer supported", as of CF 2016.

(Note that for now, nothing is "obsoleted" or "removed" in CF2016, so this is just about our being made to know that certain features that DO work now in CF 2016 may NOT in future releases and won't be receiving any additions, enhancements, or modifications. )

While some of these features listed as deprecated will be things that most won't miss (and some may even wonder why they weren't deprecated sooner), some of the features listed as deprecated may really surprise some folks, as I'd not heard discussion of their deprecation myself until finding them discussed in the CF docs.

[....Continue Reading....]

Stuck running the ColdFusion 'Migration wizard'? Here's how to get past that

CF Admin migration wizard screenSomeone presented a problem on a discussion list where they found that upon installing CF, they got to the "migration wizard" screen, and though it offered the option to "continue" if it hung up, it did not continue for him.

In this post, I'll share how to get past that prompt, if this happens to you. (And despite that image on the right showing ColdFusion 11, this could conceivably happen in CF10, CF9, and so on, and this same solution applies to all.)

For the anxious folks who want to "skip the waffle" and context/setup, the solution is at the very bottom. :-)

[....Continue Reading....]

Great set of substantial, practical, but brief videos on IIS

This isn't "new" information, though it was new to me this week. I came across this excellent set of youtube videos, 50 substantial yet brief overviews of key IIS topics from IIS/.NET/Windows guru Scott Forsyth.

I offer the list of topic titles (and links to them) below, and have even created a YouTube playlist with them, but note that the links below go to pages that the author had created where he offered a helpful introduction to each video (more than appears in the Youtube description for each).

I had also wanted to offer here this brief overview of them, to set the context and encourage you to view them, so as not to dismiss them if other tech video series haven't impressed you. Whether you're new to IIS 7 or 8, or an old hat user, there really is something for everyone, including wonderful little tips he shares in passing during most videos (which average about 10-20 minutes each).

[....Continue Reading....]

CF911: Help, How do I connect sites to a new instance w/ the ColdFusion 10/11 webserver config tool?

This one causes a lot of heartburn for folks: you add a new instance in CF10 or 11 (in editions other than Standard, which do support adding instances), and you find that you can't seem to have the web server configuration tool (wsconfig) connect sites to that new instance(s). You never see the new instance listed in the UI of the wsconfig tool. What gives?

The solution is relatively easy, and the problem could maybe be fixed (or at least warned about) by Adobe (and I just filed a bug report for it). Until that happens, I wanted to share this. For more, read on.

[....Continue Reading....]

Solving slow CF startup: my elaborating on an Adobe blog entry on a possible solution

The fine folks at the Adobe CF blog posted a blog entry today, on "Sometimes ColdFusion services refuse to start normally post server restart" (by Rahul Upadhyay), which offers some helpful information on one possible solution to the stated problem of slow CF startup.

That said, there are some concerns I have, with respect to how I fear some may read and take action based on it (especially the notion of deleting the cfclasses files, as a possible solution to the problem).

I'm not contradicting Rahul here, just elaborating on some points, as someone who (like some on the CF team) helps people with CF server troubleshooting every day.

I started to write these thoughts as a comment there, and (as often happens) it grew long so I thought it better to be a blog entry rather than a long comment, and point people here. Once I did that I decided to go further still, hoping to really help those interested to consider the issue more carefully. (It also gives me a chance to highlight again the Adobe CF team blog, something I recommend EVERYONE reading this should follow!)

One quick point (and update) for the TL;DR cloud: My recommendation is that you move the cfclasses folder out of that location, as a temporary test, to see if it makes CF startup happen faster. If it does, I explain why and what the implications are in the choices of renaming, deleting, moving, or disabling the related "save class files" feature. Also, I add an update in E.1 below (since posting this) which you may really want to read: consider turning off your anti-virus software's real-time protection against the cfclasses folder to see if that alone helps with startup.

[....Continue Reading....]

More Entries

Copyright ©2018 Charlie Arehart
Carehart Logo
BlogCFC was created by Raymond Camden. This blog is running version 5.005.
(Want to validate the html in this page?)

Managed Hosting Services provided by
Managed Dedicated Hosting