CFSTAT kills my ColdFusion 8 on Win2008R2

Enabling CFSTAT on ColdFusion 8.01 running on Win2008R2 crashed my ColdFusion ...

I'm talking about this:

I'm trying to figure out why is it that CFDOCUMENT with images, crashes my ColdFusion whenever the image is in a directory for wich the IIS has Integrated Authentication... but that's another story.

In the process of figuring that one out, I tried enabling CFSTAT to get more information on my problem.  My server simply crashed just I clicked the SAVE button.

This post on Adobe forums says:

Turning on CFSTAT in the admin is what killed my server.
Just FYI... I'm using 64-bit Vista with my CF8 installation. 

and the solution to this problem is:

Edit the neo-metric configuration file
c:\ColdFusion8\lib\neo-metric.xml
(This file doesn't contain any formatting, so its best to open it with Dreamweaver or some other editor that will format the file to make it easier to read)  

Delete the following code:
<var name="cfstat">
<string>true</string> </var>  

...which should be located somewhere inside the coldfusion.server.ConfigMap struct.  

<wddxpacket version="1.0">
</wddxpacket>



<header>
<data>
<struct type="coldfusion.server.ConfigMap">
<var name="cfstat">
<string>true</string> </var></struct></data></header>

The problem is not related to x64 windows, as I have a Win2003 x64 server where this setting is enabled with no problem.  I believe the problem is more related to IIS7 ...  any comments ?

CF BUG 80577 : Deleted Probes are still alive !!!!!

A friend showed me this today: http://cfbugs.adobe.com/cfbugreport/flexbugui/cfbugtracker/main.html#bugId=80577

It was reported for CF9, but applies to CF8 too.

And it just happened to us.  We moved our probes from server X to server Y... however, a week later we discover our exception log shows "probe not found" all over...   in deed, the probes are still trying to run even after you deleted them from CF Admin.

So, bug isn't fixed yet... here's the workaround:

Renaming a probe (via the CFADMIN), creates a new probe and leaves the old one orphaned.  You will then get exceptions each time the old probe runs (according to its own schedule), e.g. "Error","jrpp-5","10/29/09","19:38:00",,"Probe not found: ""sk: homepage"" The specific sequence of files included or processed is: C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\CFIDE\probe.cfm, line: 85 "

Workaroundmanually modify neo-cron.xml to remove the old entry, and restart CF 

Not Found:404 with coldfusion.ajax.submitform on IIS7

A friend ran into this error when migrated a CF8 application to IIS7:  

Not Found:404 

It happens when executing a coldfusion.ajax.submitform of a form with quite many fields and values....

As you know, coldfusion.ajax.submitform sends a request to the handler page via URL, that contains the whole structure of the referenced form with it's selected values.   In some cases this means the resulting URL can be very large depending on the complexity of the referenced form.

IIS7 apparently has a lower tolerance to URL Requests size limits than IIS6 had... and in order for some ajax.submitform to work, you would need to increase the size limits on your IIS7.  This is done on REQUEST FILTERING like this:

The red out values have to be increased to match the length of your form.. so it allows IIS7 to send it as an URL Request ...

CF8 and CF9 Security Hotfix released

people... a new security hotfix was released by Adobe today.  get it here.  Adobe strongly suggests you all update using this patch.

This update applies to CF8 and CF9.

Please note as you follow installation instructions that there's some additional steps to be performed after you extract the .jar file on the CF Admin. page.

Reset CF Admin Password

This is an oldie but goodie..  had to resource of this before and now someone reminded me how it works (I cannot quote the original source as I got this on an email)

What if you forget the ColdFusion Admin Password?

Imagine suppose you have forgotten the admin password and cannot log in to ColdFusion Administrator. Here is a solution for this, follow the below steps.

1. Make a backup copy of CF_HOME\lib\neo-security.xml file
In case of multi-server editions, the path is: 

C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib\neo-security.xml 

2. Open the neo-security.xml file in a text editor and change 'true' to 'false' for the admin.security.enabled variable tag. For example, search the file for "admin.security.enabled" and change the entry as follows: 

 

3. Restart the ColdFusion application server. 

You should now be able to bypass the login to the ColdFusion administrator. You can reset the password by choosing Security > Administrator.

This works for CF7 and CF8 ... don't know if it works on CF9, has anyone tried ?

jQuery 1.5 released

jQuery 1.5 released today .  Read it here.

Interesting stat they published on this release note, how much faster jQuery is on Chrome (and sometimes on Safari), than on any other browser.

OperatingSystemMXBean: how to know when your ColdFusion server is using much memory, and how to fix it.

This is an excellent post found on http://www.coldfusionjedi.com about how to access the memory consumption on your ColdFusion server.  Read it here.
Basically, there’s this Java Interface, OperatingSystemMXBean, that will tell you the server’s Total Physical Memory, and the server’s Free Physical Memory.
It goes like this:

<cfset mf = createObject("java", "java.lang.management.ManagementFactory")>
<cfset osbean = mf.getOperatingSystemMXBean()>
<cfoutput>
free physical mem = #osbean.getFreePhysicalMemorySize()#<br/>
total physical mem = #osbean.getTotalPhysicalMemorySize()#<br/>
</cfoutput>

I find this interesting because my production server is recently starting to act up… every once in a while is reporting memory full on the JVM.  While I figure out the reasons, I need to perform a garbage collection every now and then.  Using this little script, I can create a Scheduled Task that periodically checks on the memory consumption, and whenever it reaches some limit, I want it to trigger the G.C.

About the G.C., here it is:

<cfset obj = createObject("java","java.lang.System")/>
<cfset obj.gc()/>
<cfset obj.runFinalization()/>

It does work to keep the server running, but I still need to find that memory leak.