Entries Tagged as “ColdFusion”
ColdFusion | Docs
ColdFusion documentation goes live at http://helpx.adobe.com/coldfusion/home.html
For the last two years, we have had a wiki-based model for ColdFusion documentation, with some of the revered ColdFusion experts in the industry editing the documentation and helping us keep it fresh and up-to-date. I am sure a large number of us have benefited from meaningful code samples and other documentation input that ColdFusion community experts shared. We would like to thank each of our ColdFusion community experts for their involvement and selfless commitment. We would like to specifically shout out a BIG THANK YOU to Adam Cameron, Aaron Neff, Charlie Arehart, and Raymond Camden. Not to forget, Dave Ferguson, Carl Von Stetten, Adam Tuttle, Peter Freitag, Steve Blades, Matt Dyer, Kev McCabe, Sam Farmer, Andrew Myers, Matt Busche, Nicholas Tunney, Ryan Guill and Steven Neiland for the value add they have provided.
However, we have had several issues with the wiki service and implementation, causing us to look for a better solution. Owing to this, we are constrained to move away from the wiki model temporarily. Having said that, please rest assured that we are diligently working toward evaluating various options and we will partner with ColdFusion community experts to set the right collaborative authoring process.
In the meantime, we most certainly want to continue seeking the expertise of ColdFusion community experts in adding value to ColdFusion documentation. We request you to continue interacting with us through https://forums.adobe.com/community/coldfusion/documentation. We will now closely monitor the forums threads and will update the documentation accordingly. You could also leave your feedback on every help page using the yellow ticker that says “Was this Helpful?”.
We will review each comment that is posted using this ticker. You can also directly reach us at the email alias firstname.lastname@example.org. We are eager to continue our collaboration with you and hence we are making several means available for you to continue providing your valuable input.
We look forward to your continued support as we navigate through the temporary changes. Thank you once again for being so supportive of us in keeping ~4000 pages of ColdFusion documentation updated and useful to the community.
Security | Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | ColdFusion | ColdFusion 11
The following ColdFusion updates are now available for download. These updates address a common XXE vulnerability in BlazeDS. For details refer the security bulletin hyperlinks in the sections below.
Users who are using LCDS with ColdFusion, should refer this technote, for updating their LCDS installation.
ColdFusion 11 Update 6
This Update addresses a vulnerability mentioned in the security bulletin APSB15-21. This update is cumulative and includes fixes from previous ColdFusion 11 updates.
For details, refer this technote.
ColdFusion 10 Update 17
This Update addresses a vulnerability mentioned in the security bulletin APSB15-21. This update is cumulative and includes fixes from previous ColdFusion 10 updates.
For details, refer this technote.
Adobe ColdFusion | Adobe ColdFusion 11 | ColdFusion | ColdFusion 11 | exchange | General
With ColdFusion 11 Update 3, we have introduced a new parameter called "getHeaders", in the "cfExchangeMail" tag. It accepts a boolean value. When set to true, cfExchangeMail returns a query with an additional "InternetHeader" column. This column contains a struct containing key-value pairs of the email-headers associated with each message.
Email message headers provide technical details about the message, such as who sent it, the software used to compose it, the version of the MIME protocol used by the sender etc.
On Exchange 2010, the fields that are returned are: CC, Content-Transfer-Encoding, Content-Type, Date, From, MIME-Version, Message-ID, Received, Return-Path, Subject, To, X-MS-Exchange-Organization-AuthAs, X-MS-Exchange-Organization-AuthSource, X-Mailer.
You may reference this weblink for the detailed list of the fields and their description.
You can put this new feature to any good use that suites your purpose. I will dwell on one such use case below.
In MS Exchange 2010 and later, the "ToId" column in the retrieved messages query contains the primary email address of the sender. A primary email address can have multiple aliases. If you need to retrieve the email-alias the message was sent to, you can make use of this new attribute.
Here's an example that demonstrates the usage the tag in the context of the use case discussed above:
<cfmail from="#frm_usr_email#" to="#to_usr_alias#" cc="#cc_usr_alias#" subject="#msg_sub#" server= "#exchangeServerIP#" port = "25">
----------- testing mail to an alias address ------------
<cfexchangeConnection action="open" username ="#to_usr#" password="#password#" server="#exchangeServerIP#" serverversion="#version#" protocol="#protocol#" connection="excon">
<cfexchangemail action="get" name="usr_msgs" connection="excon" getheaders=true folder="Inbox">
<cfexchangefilter name="fromID" value='#frm_usr#'>
<cfexchangefilter name="subject" value="#msg_sub#">
<cfif usr_msgs.recordcount GTE 1>
info from cfexchangemail fields:<br>
info from cfexchangemail.internetHeaders fields:<br>
#ReplaceList(usr_msgs.internetHeaders["from"], ">,<", ",", ",", ",")#<br>
#ReplaceList(usr_msgs.internetHeaders["to"], ">,<", ",", ",", ",")#<br>
#ReplaceList(usr_msgs.internetHeaders["cc"], ">,<", ",", ",", ",")#<br>
You can reference the bugbase, for the enhancement request originally logged for this feature.
Performance | Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | ColdFusion | ColdFusion 11 | General | productivity | Scheduled Tasks
Many times you would want to tweak the performance of the ColdFusion server or want to debug the bottlenecks that make the server unresponsive.
To analyze this, ideally you would want to have Thead dumps and Server memory snapshot(Heap Space, Eden Space, Survivor Space, Old Gen, Perm Gen).
While you can use JDK tools like jstack to get the dumps, it is tedious to install it and schedule the thread dumps.
So, programmatically thread dumps and memory snapshots are are triggered and can be configured as a scheduler task and can be triggered on-demand as well.
Download the following zip file and move it to the server where you want to take thread dumps.
Place this file under: C:\ColdFusion11\cfusion\wwwroot\WEB-INF\lib\ and restart the server for it to load.
And the other file is the cfm file takethreaddump.cfm where the call to ThreadDump class is made and the path where the dump content should be written.
By default it is dumped to the file #GetTempDirectory()#/threaddump<Day>-<Month>-<Year>.log
(Depending on the server location it translates similar to C:\ColdFusion11\cfusion\runtime\work\Catalina\localhost\tmp\threaddump12-8-2015.log)
You can change this to any other convenient path in the cfm file.
You can call this cfm on-demand at point of time or configure a new scheduled task to schedule it at some interval.
More number of Thread dumps are more helpful for problem analysis. So, it is better to take at some interval.
On every new day, dump is rotated automatically to a new file name.
Administrator | Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | Adobe ColdFusion Builder | ColdFusion | ColdFusion 11 | General
Would like to explain the some of the factors that decide how much maximum memory that an application needs.
Here are two examples. One is with cffile upload action and the other is with cfpdf thumbnail action.
Sometimes, while uploading large files using cffile with upload action (<CFFILE ACTION= "UPLOAD") you would have run into the following error
"500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed."
File upload is dependent on “Maximum size of post data” value that you can set in ColdFusion Administrator.
However, it can’t exceed the total available free memory.
Say, if 512 MB is the Xmx memory value (jvm.config) and 350 MB is already occupied by the application, even if “Maximum size of post data” value is set to 200 MB, it can upload files of up to ~150 MB (512 MB- 350 MB).
It can’t upload files of size 200 MB.
To fix it, Xmx should be increased which is again subjected to the available memory in that machine.
Here is other example:-
Say, you are using CFPDF's Thumbnail Action and the
thumbnails background is not generated properly.
Here the issue would be insufficient memory.
Just to hold the decoded image data, java application needs large memory (say 1.2 GB depending on the image pixels).
It is because of the format and high pixel nature of the image that is being converted. Number objects created are equal to the total number of pixels in that image.
So, high pixel imge would consume more memory.
To fix this, Xmx value in jvm.config should be at least
-> Applications memory Size + 1.2 GB (from the above example) i.e.
a minimum of 1.5 GB and can be more depending on your application.
Changing the value and restarting the server would fix this.