Techode

Tag: ColdFusion 11

  • ColdFusion WSConfig configuration backups

    ColdFusion 11 update 5 helps address a issue with connector reconfigurations, that could potentially leave you in the lurch. The update includes a workflow to backup your custom configurations while un-configuring ColdFusion from an IIS site or an Apache instance.

    Here’s a little more detailing about what the workflow does.

    On unconfiguring the connector on IIS, a directory backup gets created under the /CF/config/wsconfig directory, and houses directories which go by the names “1-1“, “1-2“, “2-1“, etc. Though these directories sound too cryptic, its easy to figure out what it stands for. You can consider the naming convention to be of the form <ORIGINAL CONFIGURATION DIRECTORY MAGIC NUMBER>-<INCREMENTAL NUMBER>. The incremental number exists to ensure older unconfigurations do not get overwritten.

    On unconfiguring the connector on Apache, everything said of the IIS hold true. Additionally, mod_jk.conf is also backed up. The mod_jk.conf file is created by ColdFusion, and tied to Apache’s httpd.conf when the connector is configured. The said configuration file houses mappings to connector files, CF specific handler mappings and virtual directories.

    And that, we hope, saves you from frustrations of re-tuning you connector configurations!

  • ColdFusion 11 Hotfix 5 and ColdFusion 10 Hotfix 16 are out!

    Hotfix 5 for ColdFusion 11, and Hotfix 16 for ColdFusion 10 are out, and fix close to 150 bugs collectively!

    Connector fixes for IIS are available for ColdFusion 11, and that would imply the need to reconfigure connectors if you are on a ColdFusion 11 configured with IIS. ColdFusion 11 also packs Apache 2.4.10 support. However, you would not need to reconfigure Apache connectors unless Apache 2.4.10 support is required.
    No connector reconfigurations are required for ColdFusion 10.

    Find the technotes below,
    ColdFusion 11 Update 5: https://helpx.adobe.com/coldfusion/kb/coldfusion-11-update-5.html
    ColdFusion 10 Update 6: https://helpx.adobe.com/coldfusion/kb/coldfusion-10-update-16.html

    More details are seen on the ColdFusion Blog.

    Appreciate your feedback!

  • ColdFusion 11 Hotfix 3 – Early Access

    Hotfix 3 for ColdFusion 11 is out for early access, with a long list of fixed bugs. Early access / public preview for ColdFusion releases was a request we received at CFSummit, and here they are!

    View the list of Issues Fixed
    Read the Release Notes

    Instructions to apply the hotfix are available here.

    Appreciate your feedback!

  • Busting the HTTP Error 500.19 on ColdFusion 11 + IIS

    Here’s a little trouble shooting tip to bust an IIS HTTP Error 500.19 (Internal Server Error) that may pop up when IIS is configured with ColdFusion 11. The error mostly occurs when IIS is unable to interpret configurations specified in the web.config file.

    In this post I speak about fixing a specific cause of a 500.19, while the ideology can be applied to fix similar errors.

    When a connector is configured with IIS, ColdFusion attempts to register required MimeTypes in IIS. MimeTypes are registered to the server, or to specific site based on the options selected during connector configuration. Now, there is a good possibility some of these MimeTypes may be already added by other third party applications. Now what happens is a debacle. ColdFusion attempts to register a MimeType, and IIS puts this into a web.config file, and since this entry is actually a duplicate, IIS fails to serve any pages off the affected sites, and throws a 500.19.

    Here is one such error. The duplicate MimeType added in this case, is .air
    MimeError

    All we need to do to get around this error, is to either unconfigure the connector, navigate to IIS Manager > Site in Consideration > MimeTypes, remove the entry that references .air extension, and reconfigure the connector, OR, If you are confident enough to play around with you server, the web.config file itself can be edited to reflect appropriate settings.

    While that should get rid of the 500.19, this particular issue is being tracked, and will be resolved in a future release of ColdFusion.

  • ColdFusion 11 Hot Fix 1 and Connectors

    There it is! Hotfix 1 – The first update for ColdFusion 11.
    The technote detailing the release is here, https://helpx.adobe.com/coldfusion/kb/coldfusion-11-update-1.html#

    The update packs a handful of fixes to critical bugs, with two of them being on the connector. I will be detailing these two fixes here,

    1. IIS worker process hangs when IIS site config is changed – Bug# 3777189
      The bug details the issue where IIS worker process (w3wp.exe) hangs or loads for a prolonged time, and eventually times out after a configuration change is made on IIS manager. This was a serious bug, and has been confirmed to be fixed in the update.


    2. First request slow on Windows – Bug# 3758172
      The bug basically points out that the first request, when configured with IIS, takes a large amount of time to render. This would happen after the ColdFusion server has restarted, or if the IIS worker process has returned from the idle state. This bug too, is confirmed to be fixed in the update.

    An important factor to consider, is that the connector bits already configured on your environment need to be replaced with the fixed one’s. What this means is that the existing connector would have to be removed and reconfigured for the fixes to be in place. Just ensure, all your custom connector configurations are backed up before you reconfigure!

  • ColdFusion 11 – Manually remove connector configuration

    This post deals with removing connector residues on web-servers, IIS and Apache, if and when the wsconfig utility is not available for un-configuring existing connector configurations.

    Connector residues are left behind with incorrect uninstallation of ColdFusion Getting Started servers, or more simply, the ZIP Installers. The right way to get rid of a Getting Started server, would be to check and remove any existing connector configurations, and then delete the extracted ColdFusion directory. Failing to do this may result in connector residues strewn on IIS or Apache, and future connector configurations may behave unexpectedly, or on the extreme end, stop the web server from firing up!

    Below are a handful of steps to remove ColdFusion connector residues on Internet Information Services (IIS):

    1. Verify ColdFusion connector is the culprit before proceeding
    2. Open Internet Information Services (IIS) Manager
    3. Select Server / Machine Name > Default Document and delete entry for index.cfm
    4. Select Server / Machine Name > ISAPI and CGI Restrictions and delete entries that point to the ColdFusion install directory
    5. Select Server / Machine Name > ISAPI Filters and delete entries that point to the ColdFusion install directory
    6. Select Server / Machine Name > Handler Mappings and delete entries with paths, ‘*.cfc’, ‘*.cfm’, ‘*.cfml’, ‘*.cfr’ or ‘*.cfswf’
    7. Repeat the steps 3 to 6 for all sites configured with ColdFusion
    8. Delete contents of the /ColdFusion11/config/wsconfig/CONFIGURATION_NUMBER/ directory, if it contains filenames starting with ‘isapi’
    9. Restart IIS / sites
    10. Delete ‘.air’ mapping from MIME Types, if it causes any issues

    Further, here are some steps to remove ColdFusion connector residues on the Apache Web Server:

    1. Locate the Apache conf directory
    2. Find the mod_jk.conf file. Delete it
    3. Open the file, httpd.conf (apache2.conf on Ubuntu)
    4. Scroll down right to the bottom. Remove the entry that refers to the mod_jk.conf file
    5. Delete contents of the /ColdFusion11/config/wsconfig/CONFIGURATION_NUMBER/ directory, if it contains filenames starting with ‘mod_jk’
    6. Restart Apache

  • ColdFusion 11 – PDF Service prerequisites on Linux

    If you are planning to use PDF services on a Linux box with ColdFusion 11, you would need a set of packages to be preinstalled, and would also need to import a set of fonts onto your machine. Though this is called out specifically in the Adobe Live Cycle Documentation, I decided to post a set of out-of-the-box commands that get these prerequisites in place without hassles. These commands use the yum or apt-get package managers to install prerequisites and have been tested on RHEL 6+ and Ubuntu 13.10+.


    RedHat, and everything YUM powered,
    Execute the below commands from a terminal, or run it from a script file on an RHEL, or any machine with valid yum configurations.

    yum -y install glibc.i686 zlib.i686 libX11.i686 ia32-libs expat.i686 freetype.i686 nss-softokn.i686 libxcb.i686 libXau.i686 libXext.i686 libSM.i686 libXrandr.i686 libXrender.i686 libXinerama.i686
yum -y groupinstall "X Window System"
wget http://cgit.freedesktop.org/xorg/font/ibm-type1/snapshot/font-ibm-type1-1.0.3.tar.gz
tar -zxvf font-ibm-type1-1.0.3.tar.gz
cd font-ibm-type1-1.0.3
mv * /usr/share/fonts/
cd ..
rm -rf font-ibm-type1-1.0.3
rm -rf font-ibm-type1-1.0.3.tar.gz



    Ubuntu
    Execute the below commands from a terminal, or run it from a script file on an Ubuntu with apt-get repositories configured. 

    #!/bin/sh

export DEBIAN_FRONTEND=noninteractive

# Add dependencies for PDF
dpkg --add-architecture i386
apt-get update

apt-get --assume-yes install glibc-2.*
apt-get --assume-yes install lib32z1
apt-get --assume-yes install lib32ncurses5
apt-get --assume-yes install libbz2-1.0:i386
apt-get --assume-yes install lib32z1-dev
apt-get --assume-yes install libbz2-dev:i386
apt-get --assume-yes install zlib1g
apt-get --assume-yes install libx11*
apt-get --assume-yes install lib32z1
apt-get --assume-yes install lib32ncurses5
apt-get --assume-yes install libbz2-1.0:i386
apt-get --assume-yes install libexpat1
apt-get --assume-yes install libexpat1:i386
apt-get --assume-yes install libfreetype6:i386
apt-get --assume-yes install x-window-*
apt-get --assume-yes install libnss-mdns:i386
apt-get --assume-yes install libxcb1-dev:i386
apt-get --assume-yes install libxcb1-dev
apt-get --assume-yes install libxext6
apt-get --assume-yes install libxext6:i386
apt-get --assume-yes install libsm6
apt-get --assume-yes install libsm6:i386
apt-get --assume-yes install libxrandr2
apt-get --assume-yes install libxrandr2:i386
apt-get --assume-yes install libxrender1
apt-get --assume-yes install libxrender1:i386
apt-get --assume-yes install libxinerama1
apt-get --assume-yes install libxinerama1:i386
wget --no-check-certificate  https://cgit.freedesktop.org/xorg/font/ibm-type1/snapshot/font-ibm-type1-1.0.3.tar.gz
tar -zxvf font-ibm-type1-1.0.3.tar.gz
cd font-ibm-type1-1.0.3
mkdir -p /usr/share/fonts/
mv * /usr/share/fonts/
cd ..
rm -rf font-ibm-type1-1.0.3
rm -rf font-ibm-type1-1.0.3.tar.gz

rm -rf /var/lib/apt/lists/*



    Hope this helps!

    ————-

    [8th May 2018]
    Updated source for Ubuntu. Breaking up commands seems to be necessary.

    [4th Jul 2017]
    Updated source for Ubuntu based on the comments by, KnuBew and David Belanger.
    > dpkg –add-architecture i386
    > apt-get update