Migrating or Comparing CF Admin Settings, between instances, versions, and engines

You can learn more (including the description, the online meeting URL, where the recording will be posted, and more) at the meetup event page. FWIW, the session name had to be shortened a bit as presented on the meetup site there and even in the title here. :-)

As a bonus for you, my blog readers, I'll note that I'll be covering the CF migration and CAR features, the Commandbox CFConfig tool (which can be used for more than just "box" instances) and the CF2020 cfsetup tool (which has been shown publicly already), and more.

I'll also have a special surprise for people who "just want to compare the Admin settings of two instances without resorting to command-line tools, or hopping back and forth between browser tabs", using a free cross-platform GUI compare tool (and a simple trick in the CF Admin) which has delighted nearly everyone I've ever shown it to. And the tool can benefit you for far more than this one task. :-)

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.

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

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.

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.

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

Note: This blog post is from 2014. 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.

They don't run in the background, only doing their job when you ask them to, so I find them safe to install and use on production servers, though of course any tool can be abused. I've never seen these to cause a problem in many thousands of uses.

I was reminded to share this list today as I was helping a customer, as I got on their server with them to help them solve a problem. I recommended we install these as I do on nearly all my engagements (and indeed on all my own machines). I think they really are fundamental tools, as I'll explain below.

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

Note: This blog post is from 2013. 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.

Anyway, here is the answer I wanted to offer to that question...

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

Note: This blog post is from 2012. 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 common answer offered is that one should use the "system info" page in the CF Admin, and its available "update level" field.

But I will assert that's not the "right answer" after all, or certainly not the "best answer" to really know what hotfixes (plural) have been applied. Know why? If not, I'll explain here, and I'll show what I would say is the "right" answer to "what hotfixes have you applied?"

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

Note: This blog post is from 2012. 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.

For years, experienced developers have recommended client-side proxy tools like Firebug, Fiddler, Charles, and such. I list these and many others as a category in my CF411 site listing over 1800 tools and resources for CFers, in the category, HTTP Debugging Proxies/Sniffers/Web Client Test Tool.

I recently updated the list, though, to point out these "built-in" forms of these tools, now available in most browsers. If you may be in a place where you are "not allowed" to install new software (or are simply disinclined), knowing that the browser may have such a valuable tool built-in can be a real discovery, thus this entry.

Here's the content that I've added to that section:

• In Chrome, see the Dev Tools, available under the "Customize and control Google Chrome" icon at the top right (the monkey wrench), then Tools>Developer Tools.
• In Firefox 6 and above, see the "Web Console" feature in the "Web Developer" tools, available under the Tools menu.
• In Internet Explorer, see the Developer Toolbar which is an ad-on for IE 6 and 7, and the f12 Developer Tools that are built into IE 8 and 9 (in the Tools menu).
• In Opera, see the Developer Tools in Opera DragonFly, available in the Edit>Developer Tools menu in Windows, and Tools>Advanced on Mac.
• In Safari, see the "Web Inspector" feature of the Develop menu.
• I welcome additions/corrections/feedback.

The links I've given for each of these often have friendly introductions to using such tools. I can also commend an old but classic discussion of such tools, here.

Have you used these sort of tools? How have they helped you. Are you surprised to learn that the browsers now have such tools built-in? Chime in and share your thoughts. I may do a later blog entry or talk introducing using these tools for some common problems working with CF.

Note: This blog post is from 2010. 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 just want to look at a file, there's a great free tool to do it: UniversalViewer.

It can open a 1GB file as fast as a 1kb file (because it only pulls in what it needs to show the screen full of text you're looking at.) And there are times when you may well need to look at some very large files, especially when troubleshooting CF servers, like I do.

And actually, as its name implies, UniversalViwer can view far more than just text files, including images and more.

I've just only ever used it for looking at log files, for which it excels (and yes, you can search within the file, set it to tail files, and more.)

I've been touting the tool for years in classes and presentations, and I was about to mention it in another blog entry, but then I realized I'd not blogged about it on its own. Rather than have the reference lost in another blog entry, here's its moment to shine!

And yes, I do realize there are several other tools that can do this. I list this one and several others in a category of my CF411 list: Generic File View/Log Analysis Tools. (Note that there are some nifty tools in that category there for looking specifically at CSV files, as well as other entire categories for specific kinds of logs, like CF logs, web server logs, windows event logs, etc.)

Note: This blog post is from 2010. 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.

Before proceeding though, let me say that I realize there are many spam solutions, including ones based on your mail server instead (that you or your host might implement).

And yes, of course I do realize that folks using Gmail will want to say that they never have to worry about this at all!

Let me please just speak to those who do choose to (or have to) receive email from other mail servers, and perhaps can't control spam handling on the server, or still favor a client solution.

Background

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

Note: This blog post is from 2010. 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.

It's a first cut. While there are couple of concerns that will come to mind for some readers, and I try to address those at the end, it does work for me and has helped improve my server's stability and reliability, and it's been used by many others.

Update in 2020: I have changed the 503 status code below to 429, as that has become the norm for such throttles. I had acknowledged it as an option originally. I just want to change it now, in case someone just grabs the code and doesn't read it all or the comments. Speaking of comments, do see the discussion below with thoughts from others, especially from James Moberg who created his own variant addressing some concerns, as offered on github, and the conversation that followed about that, including yet another later variant.

Update in 2021: Rather than use my code, perhaps you would rather have this throttling done by your web server or another proxy. It is now a feature offered in IIS, Apache, and others. I discuss those in a new section below.

Background: do you need to care about throttling? Perhaps more than you realize

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