Entries Tagged as “General”

ColdFusion 11 Silent Installation Properties

June 23, 2014 / Krishna Reddy

  Administrator | Adobe ColdFusion | ColdFusion | ColdFusion 11 | General

Silent instllation properties are updated for ColdFusion 11.

You can download the properties file here

Create a new directory and place the installer and the properties files there.

Please make sure to update the usernames/passwords/and flip the different feature flags as per your requirement.

'cd' to the newly created directory where the installer and properties files are placed.

Command to run the silent installation from the terminal is(Change it as per the Installer name).

>ColdFusion_11_WWEJ_win64.exe -f silent.properties

Please make sure that the terminal/command propmt is opened with administartor/root privileges (Open cmd with Run as Administartor option).

Once initiated, installation process runs in the background. Once the installation is complete you can see a log file named Adobe_ColdFusion_11_Install* under the ColdFusion installation home directory.


ColdFusion 11 IIS Connector Tuning

May 22, 2014 / Anit Kumar Panda

  Performance | Administrator | Adobe ColdFusion 11 | Connector | General | Splendor | Tuning

Connector tuning is an essential part of setting up a ColdFusion server. There are various configurations in connector that needs to be tuned. Incorrect values may lead to “Service Unavailable” or “Server too busy”. In this blog, we will discuss how to handle such errors caused by incorrect tuning and how to tune the connectors for the site correctly.

The connector setting may vary from site to site. It is very important to configure the connectors for your application appropriately. This blog will include connector tuning parameters for IIS. During installation, user can choose to configure connector for “Individual Site” or “ALL” sites in IIS connector configuration.

Configure Web Server

After the installation, the user can launch the “Web Server Configuration tool” and has the availability to create the connector for “Individual Site” or “ALL” sites in IIS.

Add Web Server configuration

When connector is configured with individual sites, separate connector for each site will be placed under {CF-Home}/config/wsconfig/{some no}/. Similarly for “ALL” configuration the connector is configured at global level, which means the same connector binary will be used across multiple sites.

The three most important parameters will be discussed here and will help us to understand the role of the same:-

Re-use connections: - This setting determines the count of connections that can be re-used. When Tomcat connector makes a connection with Tomcat server, it does not closes the connection even after it finished serving the request. Instead it keeps the connection active, so that for the next request, the same connection can be re-used. This increases the performance by minimizing the overhead of creating new connection with tomcat server for every request. This settings needs to be tuned for connector configured with multiple sites. The max value for the re-use connection is determined based on the number of sites configured with same CF server and the load on each site.

The default re-use connection is 200.

Connection pool size: - This setting determines the maximum number of connections that can be created in the connection pool. When multiple requests arrive to the connector from IIS, connector creates new connections in the connection pool only if there are no free connections available in the pool. The connector will not create a new connection if connections reach the connection pool size limit. When connector is configured with “ALL” sites, the same connection pool will be used to serve the request for all sites. So the default value of the connection pool size, works well with the single site configuration, but fails to work well with “ALL” site configuration in some scenarios. Hence this value should be increased carefully based on the need and number of sites that are present within IIS.

The default connection pool size is same as, which is 200.

Connection pool timeout: - This setting determines the timeout value (in seconds) for idle connections in connection pool. This value must be in sync with the connectionTimeout attribute of your AJP connector in Tomcat's server.xml.

The default timeout for connection is indefinite, if not set in server.xml explicitly.

There are other parameters which CF connector inherits from Tomcat AJP connector. Please find the details of those settings from AJP documentation (http://tomcat.apache.org/connectors-doc/reference/workers.html)

The worker.properties is available at {CF-Home}/config/wsconfig/{some no}/ and the server.xml can be found at {CF-Home}/cfusion/runtime/conf/. Below are the changes required to tune the Site:-

There can be multiple use cases. Let us consider three most widely used scenarios:-

Use Case# 1: Connector created with “ALL” OR with “Individual” Site and single site in IIS

In an idle scenario, where the user has only one site (configured with ALL or individual connector) and not running under high load, the worker.properties, can look like this

worker.list=cfusion

worker.cfusion.type=ajp13

worker.cfusion.host=localhost

worker.cfusion.port=8012

worker.cfusion.max_reuse_connections=250

worker.cfusion.connection_pool_size=500

worker.cfusion.connection_pool_timeout=60

And server.xml should look like

<Connector port="8012" protocol="AJP/1.3" redirectPort="8445" tomcatAuthentication="false" maxThreads="500" connectionTimeout ="60000"> </Connector>

So, we added the connection_pool_size and connection_pool_timeout (in seconds) in the worker.properties. The corresponding connectionTimeout (in milliseconds) is added to server.xml along with maxThreads whose value is equivalent to the connection_pool_size in the worker.properties.

Use Case# 2: Connector created with “ALL” and multiple sites in IIS

Consider a scenario that the connector is created with “ALL” and there is only one site which is running under load. The default 200 re-use connections are utilized by site 1. Later on, the user adds another site in IIS.

Site 1 will make all 200 re-usable connections with ColdFusion and any request for new connection from site 2 will be ignored by ColdFusion. Hence it is required, to increase the re-use connection count to optimal value, so that site 2 does not starve for new connections. This can be achieved by configuring optimal value of max_reuse_connections count. Considering that the site 2 is not running under high load, 100 re-use connection will work. So the max_reuse_connections becomes 300 {200 (for site 1) + 100 (for site 2)}. But, it is a good practice, to start tuning the connection_pool_size first, and then the max_reuse_connections appropriately.

This case would require connection_pool_size=600, as max_reuse_connections= connection_pool_size / {no of site}. So, the worker.properties will look like this

worker.list=cfusion

worker.cfusion.type=ajp13

worker.cfusion.host=localhost

worker.cfusion.port=8012

worker.cfusion.max_reuse_connections=300

worker.cfusion.connection_pool_size=600

worker.cfusion.connection_pool_timeout=60

And server.xml should look like

<Connector port="8012" protocol="AJP/1.3" redirectPort="8445" tomcatAuthentication="false" maxThreads="600" connectionTimeout ="60000"> </Connector>

Note: The connectionTimeout is in milliseconds

Use Case# 3: Connector created with “Individual” site and multiple sites site in IIS

Consider a scenario that the individual connectors are created for each site. There are three sites - Site 1 is running under high load, site 2 and site 3 running are under low load. For all the sites, there are individual connectors. Now, ideally in this scenario, we should start tuning with the site running under high load first. We can disable the timeout for high traffic sites, if we are not sure for timeout. If not defined, the default timeout for connection is indefinite. To start with, don’t specify the re-use parameter. Set the connection_pool_size=500 and monitor the site. Gradually increase the value by 100 and likewise, till the site is stable. Say, at connection_pool_size=800, the site is stable. Now, set the max_reuse_connections=270 (connection_pool_size / {no of site} i.e. 800/3=270 approx)

Site 1

worker.list=cfusion

worker.cfusion.type=ajp13

worker.cfusion.host=localhost

worker.cfusion.port=8012

worker.cfusion.max_reuse_connections=270

worker.cfusion.connection_pool_size=800

worker.cfusion.connection_pool_timeout=60

Site 2 and site 3 are running under low traffic, but are bind to same ColdFusion instance (cfusion in this case). The below settings should be optimal:-

Site 2

worker.list=cfusion

worker.cfusion.type=ajp13

worker.cfusion.host=localhost

worker.cfusion.port=8012

worker.cfusion.max_reuse_connections=100

worker.cfusion.connection_pool_size=250

worker.cfusion.connection_pool_timeout=60

Site 3

worker.list=cfusion

worker.cfusion.type=ajp13

worker.cfusion.host=localhost

worker.cfusion.port=8012

worker.cfusion.max_reuse_connections=100

worker.cfusion.connection_pool_size=250

worker.cfusion.connection_pool_timeout=60

And server.xml should look like

<Connector port="8012" protocol="AJP/1.3" redirectPort="8445" tomcatAuthentication="false" maxThreads="1300" connectionTimeout ="60000"> </Connector>

Note: The connectionTimeout is in milliseconds and the maxThreads is the value equivalent to summation of all the connection_pool_size(s). So, in this case maxThreads=1300 {800 (for site 1) + 250 (for site 2) + 250 (for site 3)}.

Some key points to remember:-


Adobe ColdFusion Summit 2014

April 11, 2014 / Elishia Dvorak

  Adobe ColdFusion | Adobe ColdFusion 10 | Announcements | CF Summit | ColdFusion | ColdFusion 11 | General

We are pleased to officially announce the next Adobe ColdFusion Summit to be held October 16th and 17th at Aria Resort & Casino, Las Vegas, Nevada.  It's going to be even better than last year and pricing remains very low at $299 early bird rate through July!

Read More


Applying Updates on a Locked down ColdFusion 10 Server

May 21, 2013 / Krishna Reddy

  Administrator | Adobe ColdFusion 10 | ColdFusion | General | productivity | Updates

Note: This is valid from Hotfix 9 onwards.

Depending on the user account that you have used to Lock down your server, you might need to consider the following few more steps for providing appropriate permissions to be able to apply the updates from ColdFusion Administrator.

Hotfix needs two things to be installed properly from ColdFusion Administrator.

1) The user that is configured for ColdFusion Service should be permitted to Start/Stop the service. More on this to setup is explained below.

2) Since ColdFusion runs with the user you have setup for ColdFusion service, that user should have write/delete/update permissions for some of the ColdFusion directories. Notably, till now (Hotfix 9) the update files are there for the following directories:

<CFHome>\cfusion\bin\ (Write)

<CFHome>\cfusion\hf-updates\ (Write)

<CFHome>\cfusion\lib\ (Write)

<CFHome>\cfusion\lib\updates\ (Write + Delete)

<CFHome>\cfusion\runtime\lib\ (Write)

<CFHome>\cfusion\wwwroot\CFIDE\adminapi\ (Write)

<CFHome>\cfusion\wwwroot\CFIDE\administrator\ (Write)

<CFHome>\cfusion\wwwroot\CFIDE\componentutils\ (Write)

<CFHome>\cfusion\wwwroot\CFIDE\scripts\ (Write)

Note: New directories may or may not get added in the future Hotfixes but the above set will always be there for ColdFusion 10.

If you are running multi-instace scenario you have to set the same for all child instance folders and their service accounts

When lockdown guide is being imposed the above two requirements should also be implemented in order to be able to apply Hotfixes from the ColdFusion administrator.

Setting up the ColdFusion Service user as required in #1:

Down load and Install Windows tool named SubInACL.exe (Installer name is SubInACL.msi) to give service start/stop permissions from

http://www.microsoft.com/en-us/download/confirmation.aspx?id=23510

Once you install it, the tool subinacl.exe gets installed under
C:\Program Files (x86)\Windows Resource Kits\Tools

Then, run the tool as follows from command prompt by replacing <MachineName> and <username> with your username and machine name.

a) For machine’s local user

C:\Program Files (x86)\Windows Resource Kits\Tools>subinacl.exe /service "\\<MachineName>\ColdFusion 10 Application Server" /grant=<username>=TO

b) If the user is a Domain user you have to replace <Domainname> as well along with <MachineName>, <username> in the following command.

C:\Program Files (x86)\Windows Resource Kits\Tools>subinacl.exe /service "\\<MachineName>\ColdFusion 10 Application Server" /grant=<Domainname>\<username>=TO

More details on this are explained in the below resource.

http://support.microsoft.com/default.aspx?scid=kb;en-us;288129

This is a one-time setup that you have to do.

Once this is done -> Restart ColdFusion service -> Open ColdFusion server Administrator -> Apply Update  -> You should be able to apply the Hotfix successfully now.

 


Adobe Announces ColdFusion Summit 2013

May 20, 2013 / Elishia Dvorak

  Adobe ColdFusion | General

We recently announced that Adobe will be holding our first ever ColdFusion Summit conference!

Event Details:

October 24th and 25th
Manadalay Bay Resort & Casino, Las Vegas, Nevada
Registration cost: $250

Each paid registration will receive a FREE copy of ColdFusion Builder (MSRP value of $299!)

Registration along with further details will be available soon.  

Please follow this blog for updates.


Blue Mango Theme Design By Mark Aplet

Super Powered by Mango Blog