My talk will be...
You can learn more (in brief) about what's new in the bullets for 9.2.0 offered at the release notes page.
TLDR: For some folks, news of the new version is all the need to hear. For those who may like to hear a bit more about the update, read on.
Note: This blog post is from 2022. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.The FusionReactor folks will offer a webinar this Thurs, Mar 24, at noon US Eastern, "Introducing Distributed tracing and on-prem observability".
I highly recommend that FusionReactor users (and others) register. (Even if you can't attend, you will get access to the recording.) It's about some totally new capabilities:
Note: This blog post is from 2019. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.Following on my recent announcement about speaking at CF Summit 2019, I am delighted to announce also that I've been selected to speak at CFCamp 2019, in Munich this October.
This will be my sixth year in a row presenting at this wonderful event, and my seventh year total. It will also be my 10th presentation there. (You can see all my past presentations, including when and where offered, at carehart.org/presentations.)
FWIW, half of those talks have been "sponsor" presentations on behalf of Intergral, the makers of FusionReactor, while the rest were not. And despite the title of my talk this year, "Comparing Monitoring Solutions for CF and Lucee", it is NOT an FR-sponsored talk. See the description below, for more.
Note: This blog post is from 2018. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.FusionReactor (my favorite server monitor) continues its onward march of refinement and improvement with its latest release which came out last week, 7.3. In this post, I highlight over a dozen of its new features and improvements.
Note: This blog post is from 2018. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.Many will know that I'm a huge fan of FusionReactor, the monitoring tool (and more) for ColdFusion, Lucee, or any Java server (Tomcat, Jetty, Glassfish, JBoss, Wildfly, WebLogic, etc). And now I want to start a new series of posts on it. For more, read on.
Note: This blog post is from 2017. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.Have you tried to update or simply see the available plugins for VisualVM (the Java monitoring tool built into the JDK), and found that it fails to respond right away (the progress bar will show "checking") and then it reports:
Unable to connect to the Java VisualVM Plugins Center because of Server returned HTTP response code: 503 for URL: http://www.oracle.com/splash/java.net/maintenance/index.html
There is a solution.
TLDR: the quick answer is to change the URL used by the tool (Tools>Plugins>Settings) to use a new URL, such as https://visualvm.github.io/uc/8u131/updates.xml.gz.
For those who'd appreciate more detail, read on.
Note: This blog post is from 2016. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.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:
Note: This blog post is from 2016. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.I'd like to take a diversion from my recent posts focused on CF2016 and talk about something that applies (and should interest) anyone using CF 10, 11, or 2016.
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.
Note: This blog post is from 2015. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.If you've configured your web server (IIS or Apache) to be connected to CF--which can be done using the CF "web server configuration" or wsconfig tool--did you know that there is an optional monitor to observe the status of that web server connector? That connector is technically the Tomcat "AJP connector", which Adobe implements for us. And this monitor, called the Tomcat "Status worker", is an optional feature which we can configure (the CF wsconfig tool doesn't do it for us).
In this post, I discuss the tool, elaborating on a post that Adobe offered about it last month (July 2015: for future readers, note that the feature remains essentially unchanged and just as potentially valuable in 2025, when I have tweaked this post just a bit, adding a table of contents and changing the order of some topics).
You may well want to consider enabling the "Status Worker" feature, which the Adobe post shows is easily done. Still, in this post I elaborate on some observations and caveats not covered in that brief post, which you will want to consider before enabling or trying to understand the output of the tool.
Managed Hosting Services provided by
