Entries Tagged as “Adobe ColdFusion”

After 10 years, ForInsite still stands behind Adobe ColdFusion!

January 14, 2016 / Dave Brioux

  Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11

ForInsite, a professional digital marketing and development firm, has been using ColdFusion for their primary product lines for over 10 years and still going strong.  ForInsite and their CEO strongly believe that CF is best choice for their business and their customers alike!

"We are very excited to start using the new ColdFuson 12 features we saw at the CF Summit 2015 in Vegas. Can't wait for release day!"

Read More


Pre-release for API Management capabilities in ColdFusion Raijin

January 08, 2016 / Rakshith Naresh

  Adobe ColdFusion | Announcements

Organizations today are unlocking the value of their data, IP and services  by sharing the same with their ecosystem(customers, internal teams, partners, vendors, suppliers etc.) at a furious pace– often over the mobile networks. With Raijin we now add the capability to not just build and share REST/SOAP services easily we will now allow you to manage, monitor, regulate and secure these services easily.

Our research shows, once a API is written, the next questions, that a company or organization has to answer before making the API production ready are:

1. Who do I give access to APIs?

2. How do I control the access to these APIs? For instance how do I restrict the usage of certain APIs to a selected few? Even within an API how do I provide granular control over the methods available in an API?

3. How do I let developers wanting to use my APIs understand the APIs that I have exposed and test them out before writing applications to consume these APIs?

4. How do I monetize the APIs by creating various access plans and associating end developers to a particular plan based on their subscription?

5. How do I track the usage of APIs so that I align backend to the demand and also gain insights to how my end developers are using the APIs?

6. How do I track and manage various versions of the APIs I create?

7. How do I transform my legacy APIs into newer RESTful services with all the best practices associated while still maintaining the usage of the legacy API?

 

With Raijin, we are introducing an API manager that can accomplish all of the above and more.

 

If you are interested in trying out the API manager with the REST or SOAP based APIs that you have, then please reach out to us at CFPrerelease@adobe.com so that we can add you the pre-release for API manager component in Raijin.

We look forward to your participation.

 

 

 

 


Application deployed on Network/Remote Path - Identifying Network Latency - Improve Performance

November 19, 2015 / Krishna Reddy

  Administrator | Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | ColdFusion | ColdFusion 11 | creating a website | customers | General | Migration | productivity | Success Story | Tuning | web application development

Many a time, ColdFusion application code is deployed on a network path when your ColdFusion deployments are of large-scale and mandated to use network paths.

After setting up the server for the first time, if there is any performance hit, as the first thing you would want to cross-check few things. One of the things to determine is if there is any network latency.

Though you would have got same network within your organization same as earlier, your OS version also would have changed.

 

Follow the steps below to see if the performance hit is due to network latency-

When the server is under moderate or full load(with at least 8-10 requests under process), take 2 or 3 thread dumps with 30 seconds interval.

It is not appropriate to take thread dump when the server has negligible load and anlyze that as there may not be any in-process requests.

If you are not sure how to take thread dump, you can simply follow the following blog.

( Taking Thread Dumps From ColdFusion Server Programmatically )

Open the thread dump file:

Under moderate or full load server conditions, if you see more than 5-8% of running ColdFusion threads containing “WinNTFileSystem” in the thread’s stack trace --> It means that there is lot of time being spent in trying to resolve the application file paths.

Following are the sample threads having WinNTFileSystem in its dump.

"ajp-bio-8014-exec-6861" Id=13898 in RUNNABLE
 java.lang.Thread.State: RUNNABLE
 prio=5 blockedtime=28963 blockedcount=6819 waitedtime=421762 waitedcount=115
    at java.io.WinNTFileSystem.getBooleanAttributes(Native Method)
    at java.io.File.isFile(File.java:876)


"ajp-bio-8014-exec-6861" Id=13898 in RUNNABLE (running in native)
 java.lang.Thread.State: RUNNABLE
 prio=5 blockedtime=28961 blockedcount=6814 waitedtime=421762 waitedcount=115
    at java.io.WinNTFileSystem.canonicalize0(Native Method)
    at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:414)
    at java.io.File.getCanonicalPath(File.java:618)


(Note: ColdFusion threads can be identified by the name starting with "ajp-" )

For Example, if there are 50 threads with thread name starting "ajp-bio-" in the thread dump, if you see WinNTFileSystem in more than 2-3 threads, it is the time you start looking at minimizing the network latency.

 

Once you know there is latency, you would want to know how much is the latency when compared to the application existing locally.

Created a very basic network latency test program to validate this.

You can take the jar from here.

And run it from command prompt as follows:

> C:\ColdFusion11\jre\bin\java -jar <Path of NetworkPathsTest.jar> <Network or Local Directory Path >

If the network path (Ex:- \\orgserver\d$) is accessible only to the ColdFusion service user, open command prompt as that user ( runas /user:<cfserviceaccount domainname>\cfserviceusername CMD )

Examples:

Path Arguments can be one or more. More Path arguments is a good measure to see the difference clearly.

C:\ColdFusion11\jre\bin\java -jar C:\ColdFusion11\NetworkPathTest.jar \\orgserver\d$\deploy\cfm\

C:\ColdFusion11\jre\bin\java -jar C:\ColdFusion11\NetworkPathTest.jar \\orgserver\d$\deploy\cfm\ \\orgserver\d$\deploy\cfm\api\

Try the same paths keeping the content same on the local machine and see the time differences.

For the same paths on local and remote, the difference in time should not be exponential.

These tests are to be performed on your ColdFusion server machine.

Once you have validations and found any latencies, it is the time to call for network optimization expertise.

 



ColdFusion 11 Update 7 and ColdFusion 10 Update 18 are now available

November 17, 2015 / Nimit Sharma

  Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | Announcements | ColdFusion 11 | Hotfix | Updates

This post is to announce the release of new updates for ColdFusion 11 and ColdFusion 10.

ColdFusion 11 Update 7

ColdFusion 11 Update 7 includes support for Windows 10 and OS X 10.11. Tomcat has been upgraded to version 7.0.64. This update addresses a vulnerability mentioned in the security bulletin APSB15-29 and also includes bug fixes related to connector, database, language, caching and certain other areas.

For more details, refer to this article.

ColdFusion 10 Update 18

ColdFusion 10 Update 18 includes support for Windows 10 and OS X 10.11. Tomcat has been upgraded to version 7.0.64. This update addresses a vulnerability mentioned in the security bulletin APSB15-29 and also includes bug fixes related to connector, language, caching and certain other areas.

For more details, refer to this article.

For those who have applied the early access release (pre-release) build of Update 7 or Update 18, follow the steps below to reinstall Update 7 or Update 18, as applicable.

1.     Uninstall Update 7 (PreRelease) or Update 18(PreRelease). 

2.     Reinstate the update URL by clicking on the "Restore Default URL" button in the "Server Updates" section in the ColdFusion administrator.

3.     Switch to the "Available Updates" tab and click on the "Check for Updates" button.

4.     Download and install Update 7 or Update 18.

 


ColdFusion 11 Update 7 is available for early access

October 23, 2015 / Nimit Sharma

  Adobe ColdFusion | Adobe ColdFusion 11 | Announcements | ColdFusion | ColdFusion 11 | Hotfix | Tomcat | Updates

Update: Since this post was made, the final version of Update 7 was released and should be used instead.


ColdFusion 11 Update 7 early access build is now available for your testing and feedback. It includes support for Tomcat 7.0.64, Windnws 10 and Mac 10.11 along with several bug fixes.

Please note that this is a test build and should not be used in a production environment.

Refer this document for the list of bugs fixed in this update.

Follow the steps below to apply this update.

  1. Navigate to ColdFusion Administrator -> Server Updates -> Updates.
  2. Under Settings tab, check "Automatically Check for Updates" check box
  3. Change the Site URL to https://cfdownload.adobe.com/pub/adobe/coldfusion/PR/updates.xml. 
  4. Click Submit to save your changes.
  5. Under the "Available Updates" tab, click on the “Check for Updates” button.
  6. "ColdFusion 11 Update 7(PreRelease)" should be listed under the "Available updates" tab. 
  7. Click on the "Download and Install" button to install the update.
To apply this update manually, click on this link to download the update jar. To run the downloaded jar, execute the following command:
java -jar <jar-file-dir>/hotfix_007.jar
You should use the JRE used by CF for running the update jar (for standlaone CF, it should be <cf_root>/jre/bin)
MD5: 2248f3a1401fe658b40743102c5d5999
For further details on the manual application of the updater follow this help article.

The build number after applying this update should be 11,0,07,296112(PreRelease).

In case, you have configured local site for receiving the update notifications, then please take back up of the URL before changing it to the prerelease URL.

We will look forward to your valuable feedback and suggestions.


Blue Mango Theme Design By Mark Aplet

Super Powered by Mango Blog