Skip to main content

Great Example of How Our Users Help @mach_ii

My former co-worker Brandon Culpepper (who is still one of the quickest studies I've ever had the pleasure working with) ran into a bit of a bizarre issue with Mach-II yesterday, and after hearing him describe it I was determined to get to the bottom of it.

The gist of the problem was that for some reason after a session timeout occurred, the application would throw a rather non-descript error along the lines of "Element {directory name} is undefined in a Java object of type class coldfusion.runtime.ApplicationScope," and a slightly different error in OpenBD. You can read the full details in the ticket.

Brandon described the issue to me in great detail over IM, but it was one of those things I had to run locally to really get my head around it, and he was nice enough to take the time to not only whittle the problem down to a very specific, repeatable test case, but he sent me two different test applications that had only the elements we needed to be able to repeat the error and figure out what was going on. This was no small amount of work on Brandon's part and was tremendously helpful in getting to the bottom of the issue.

Using these sample apps I was able to figure out that it didn't throw the error if the hyperlink or AJAX call involved was a Mach-II event as opposed to a plain old URL, and at that point I submitted the ticket because I knew Peter, as lead developer of Mach-II, would be able to diagnose things much more easily than I could.

So Peter jumped on the case and figured it out rather quickly. It turns out that this is a rather weird bug that goes back probably to Mach-II 1.1.1 and has to do with the way Mach-II has auto-generated the MACHII_APP_KEY property based on directory names. If you hit a .cfm file or remotely call a CFC in another directory, that will trigger a change in the app key property, and since the app key property changes, Mach-II will think it hasn't been loaded. Note that this only occurs if you don't explicitly set the application key (which I always do), and only reared its head with the introduction of the onSessionStart/End methods in the Application.cfc boostrapper.

Peter came up with a fix that's currently being tested, and he makes note of it in the ticket, but I'll test posterous's code handling and stick it here:

<cfparam name="MACHII_APP_KEY" type="string" default="#GetFileFromPath(ExpandPath('.'))#" />

Note that you can also explicitly set the MACHII_APP_KEY variable to your application name as opposed to relying on the directory name and this will also fix the problem:

<cfset MACHII_APP_KEY = "whatever" />

So I wanted to take a moment to thank Brandon for notifying us of the bug and doing quite a bit of work to help us come to a quick rationale behind and resolution for the bug. Without the diagnosis and sample apps from Brandon this would have taken a lot longer to figure out, and due to his work all Mach-II users will benefit from Peter's fix to a bug that would likely bite others from time to time.

Another great open source success story. Thanks again Brandon!

Comments

Peter J. Farrell said…
FYI, the real fix is:<cfparam type="string" />The fix listed is the old code (sorry, if I messed on the code on the ticket).

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…