ColdFusion Server Monitor

So last week we had a site running amok on one of our CF8 servers so we decided to use the ColdFusion Server Monitor to see if we could figure it out. Well starting the thing pegged the server’s processors to 100% and we couldn’t get anything done, so we rebooted the machine. After reboot – since it was the middle of the day and all – we noticed that several sites were not coming back up. So we started looking around on the Internet for ways we could fix it. The sites that weren’t coming back up were all Model-Glue run so we thought it might be something in that. Producing the CFLoop error when the application was trying to compile for the first time.

Well after some digging, I came across several posts by people mentioning how Sean Corfield had talked about the JRE version included with CF8 was experiencing a bug in the way it compiled components – something that any Model-Glue application is going to do extensively at startup as it tries to build the entire library for ColdSpring. You can read about it here - ColdFusion 8 And Java 6.  So we changed out the JRE version overnight to the newest release of Java 6 Update 12.  We were still having problems with the sites compiling though, so we switched to 11.  Still no joy.

So we were getting a little concerned – it was going on a full day now since we had the sites go down.  So we said – well let’s try that Server Monitor again and see if we can tell what’s happening with it.  So we fired it up expecting the worst and saw that all of it’s options were still running.  Basically, restarting the server hadn’t set the Server Monitor back to an Off position.  Once we turned all the options off and saved it, the two down sites started again.   Unbelievable!

So the side note is, having found the article by Corfield, we have a more responsive version of ColdFusion 8 with Java 6 running on our server.  I think I can notice a difference, not sure if the clients can or not, but I know it made for a happy day once everything came back on line.

YUI Tab View – Getting the BeforeAction to work

So I’ve been building a section of a website using the YUI TabView and having some difficulty getting the beforeActiveTabChangeevent to work right.  Now I was using version 2.5.2 first, and in that version, this event doesn’t even fire.  So I tried using beforeActiveChange on the tab itself.  I could get this to fire, but returning false as the documents say to do, would not stop the event from continuing.  So I did some digging, and found a post somewhere out there – I’ve lost it now – saying that 2.6 fixed this problem.  Well I tried that for a little while, and found that in 2.6, TabView’s beforeActiveTabChange does indeed fire, but it has the same problem that beforeActiveChange had in 2.5.2 – returning false does nothing.

Well as you can imagine, I found this to be frustrating.  So I started doing a little more digging – had a post on the YUI Developer boards go unanswered, googled a bunch of things – and then stumbled on to the face that 2.7 had been released.  Well I tried using that – figuring what the heck – and it worked! beforeActiveTabChange stopped the tabs from changing if false was returned!  Hallelujah!  Now I haven’t tried to see if beforeActiveChange at the tab level works now or not, but I’m just so happy to have the TabView event work.

Subclipse Merging

So today I was attempting my first merge using Subclipse and boy was that fun to figure out.  Luckily I stumbled across this post:

Subclipse Merging

which at the time was unavailable, so I used the google cache version found here:

Cached Subclipse Merging

The basic summary to the post is this:  Since I was trying to merge the changes from my production code into my branch/development copy to have an updated copy to deploy on the development server, I needed to get a changeset from the production code – version I branched out – 1 (that part I still don’t understand, but it worked) to the head revision – and merge that with my working copy.

I chose to put it all in a new working copy with a new version that I plan to release as my new production copy – but however you do that is your own choice.