@brentil, ah, ok. I understand now. Yep, that is curious. I can confirm that it wasn't there on Mar 17, per the Google cache page: http://74.125.93.104/search?rlz=1C1GGLS_en-USUS291US306&sourceid=chrome&ie=UTF-8&q=cache:http://kb.adobe.com/selfservice/viewContent.do%3FexternalId%3Dkb402604%26sliceId%3D1 Of course, by the time someone reads this in the future, it's possible that the cached page will be different again. One would want to note the date offered by Google at the top of the page it shows. So the real question is why the CHF link was note posted here until now. I'm with you that some resources are not always updated. I blogged about it: http://www.carehart.org/blog/client/index.cfm/2008/7/16/beware_technotes_may_not_be_listed_elsewhere Perhaps more dismaying is that the CHF2 technote lists many more HFs included than appear in the main hotfix page (the URL you pointed to). So one might ask why we should have had to wait for a CHF to get those hotfixes. Also, I notice that the main cf8 downloads page (which you pointed to originally) does not, in fact, refer to the 8.0.1 CHF (though it does list 8.0 CHFs). That should be address. I agree that we should expect the hotfixes page to list any hotfixes or CHFs as soon as they're available. Sorry I missed your main point. Sadly, I don't know that we can expect too much to come of this discussion here. There's just no guarantee that anyone responsible would see it. But here's good news. A couple of blog entries have raised the concern: http://www.creative-restraint.co.uk/blog/post.cfm/coldfusion-8-0-1-cumulative-hotfix-2 http://blog.pengoworks.com/index.cfm/2009/3/18/ColdFusion-v801-Hot-Fix-2-released-in-Oct-2008 And Ben Forta is a party to the second one, where I've just added a comment asking to find who we can press about this. Finally, just an FYI: that URL you offered is indeed the same page that I'd offered. The URL I gave ( http://www.adobe.com/go/kb402604) comes from the "permanent link" offered at the bottom of all Adobe technotes, which is just a nice shorter URL. ... View more

@brentil, are you referring instead to the page with the 8/8.01 hotifxes ( http://www.adobe.com/go/kb402604)? That does show the updated date at the bottom, and the chf2 at the top from 10/20. So you seem to be raising a couple of issues: why did that page footer's date change? I don't know, but I wonder if it may not be significant. You also seem to feel that the pace of updates has slowed. Well, there were plenty of hotfixes in the months/year after 8.0 came out. 8.01 rolled those up and added a few more features. There have been several more fixes in the months after 8.01 came out. But the fact that it's slowed since then isn't quite as curious to me. I figure it's just that the release (8.0 and 8.01) has been out long enough to have stabilized (not many new fixes to worry about). Also, since you open with a concern about the stance of CF, it seems worth noting that CF9 is around the corner, and Adobe has shared quite a bit about what's coming, and yet more will be announced in due time. There's certainly no reason (in my mind) to read anything into the pace of hotfixes and the viability of CF. Anyone feel differently? ... View more

Hmm. Well, I will just clarify that I was with him (providing support online) while I addressed this. All he did was do the JVM update, and things were much better. He must have applied the hotfix the next day. We wondered if it was possible that the improvement we were seeing immediately may have had anything to do with the server being more responsive as much because it had just been restarted. We didn't dig in to confirm (via jvm debugging output showing class loading details) whether and how the jvm update may have helped. It could certainly be that the other fix was as or more important, so sure, please do apply it and let us know. (I would wonder if it's really the combination of the two that's key.) /charlie ... View more

Elarin, this is something I just helped solve for someone else. See his writing of the details at http://russ.michaels.me.uk/index.cfm/2009/3/19/ColdFusion-8-performance-Issues-when-using-Java-6. Bottom line, it was related to the oft-mentioned problem of a class loading bug in Java, fixed by upgrading the JVM to 1.6.10+ or back to Java 1.5. The blog entry mentioned (and many others) talk about how to do that. My theory is that making changes in the sandbox may force Java (the sandbox security is built atop the underlying java security manager) to unload and reload the classes for CF pages in any sandboxes (I say "any", because he was seeing that changes to ANY sandbox affected performance of ALL templates, and in his case he had a sandbox defined for all CF apps.) Let us know if that's the solution for you, Elarin. ... View more

Wow, I see that my note yesterday arrived minutes after Adam's. We were obviously writing at the same time and funny enough came to the same conclusion. Just wanted to be clear I wasn't writing my note in reply to him, but rather to the previous note by DCWebGuy. Hope either helped. We'd love to hear from the two of you (or others) who had the problem, if this helps identify the problem. ... View more

Well, digging into this a little, I see in the classic.cfm template (the built-in CFML template that controls the layout in the debugging output), it creates such a cfdebugger variable in a try/catch statement that ignores if it gets an error (calling the servicefactory getdebuggingservice method). Perhaps in the instances you guys are seeing, there's a temporary problem that's disabled the debugging service. In these cases, does a restart solve the problem? Even if you've not tried it (because they're production servers), it may be worth trying. Perhaps something has happened to make the server (CF) unstable and cause the debuggingservice to crash. In fact, what do you see if you look in the CF out logs (in the [cf]\runtime\logs or ]jrun4]\logs)? It may have errors indicating something happening. It could also be that someone has modified the classic.cfm template and just made a mistake. There are various blog entries showing how to do it (such as http://www.coldfusionjedi.com/index.cfm/2008/11/26/Another-Hack-Job--Update-to-classiccfm-debug-template). It may help if you get the exact filename and line number of the template throwing the error. I'm not referring to the page which you're requesting, but that which is reporting the undefined cfdebugger variable? To get the filename and line number, turn on robust exception handling in the Admin (the same admonition about leaving that on in production applies, but turning it on for a moment, if the error is easily creatable, should be no great risk on most sites). Hope the helps move the ball down the field a little. /charlie ... View more

So Anair, did this work for you? Your silence in reply may mean it did, and you forgot to say so, or you still have the problem and just never came back to say so. Inquiring minds want to know. 🙂 ... View more

You seem to have come to some inaccurate conclusions and are making some wild assertions. I don't myself like to contribute to (or participate in) flame wars but in this case I want to step in to again try to offer some moderating comments. I know you've been beefing with Adam to this point, but after an answer is offered (which you seem to accept) you call it "a bug in the product apparently known to at least a few of the cabal". Eh? It's not been known to anyone, that I can gather. That's why I added that I'd blogged about it just today. Some context may help: I've been following the integration of CF and Derby since its release, probably closer than anyone else. I've heard of these problems, of people experiencing the curious redirect you did, but no one had ever sorted it out that I know of, until today. So there's no "cabal" that's keeping info from you, or others. Now, you have a reasonable beef that the bug has festered this long, but really, rather than use it to make another "see, this is why CF sucks" kind of argument, let's just recognize it for what it is: a new and rather misunderstood feature (Derby in CF), and a bug in the Admin found only in a version (Standard) that can't be confirmed except by those who own a Standard license. I'd wager that most people use the Developer edition for their day to day work with CF, since it's free. They may deploy onto Std or Ent, but they don't likely develop on Std. And this bug could never be recreated in the Dev or Ent version. You have to own (and pay for) a Standard license key, and try to create a Derby DSN, to have seen this. I'd wager that many who like to help solve problems would not likely have Std (running Dev or Enterprise), so this (and the fact that many of them may not yet have worked with Derby) simply further winnows down the number of people able to help in this case. You also counter how you wouldn't "just slipstream a "fix" in with no announcement and pretend like it never happened then make out like it's a user error." Are you referring to this bug? There's been no fix slipstreamed in. Not sure what you're referring to there. But you also wonder "wouldn't it be listed somewhere as 'known issue'", and I'd say no, because in fact it doesn't seem to have been a known (or understood) issue. It is now, now that I've blogged it, and I've reported it (just yesterday, after writing the blog entry and responding here) in the Bug report page. So we can hope it will be solved. I guess it just seems the rhetoric needs to be dialed down. I don't think things are quite what you've perceived them to be. It's a bug, yes, but not one that's been known and ignored quite the way you propose. I think some unique circumstances have been the cause of the challenge in resolving it. I hope you'll reconsider your stance on this issue. Also, if you could mark the issue as answered (pointing to the earlier entry I offered) it would help any who find and wonder about the problem. Yes, it's an annoying one, but most do NOT know that it's caused by the Std license. Rather than leave them to wade through the heated discussion, it would help for them to quickly focus on the answer. Just trying to help everyone here, yourself included. ... View more

I can clear up the confusion. It turns out this issue of you being taken to the Other DSN page when you add a Derby Embedded DSN is a bug in CF 8 Standard. That's why you weren't seeing it, Adam, and really, many people have gone around a lot on this issue. I can definitively confirm it's an issue that happens only on CF 8 Standard, and I just blogged about it: http://www.carehart.org/blog/client/index.cfm/2009/3/2/bug_with_derby_on_cf8_standard Hope that's helpful. I've not read every word of the rest of the discussion above, but if there are any other outstanding questions I can answer, I will try. Just wanted to offer this ASAP. ... View more

If I had a nickel for every time someone said, "but we don't use client variables". 🙂 It matters not a wit if they ever say CFSET client.somevariable. All that really matters is if any code anywhere says ClientManagement="yes", in the same files I mentioned before about clientstorage. If so, there's a default setting in the client variables admin page for the settings of each repository for "disable global variables", and it's not checked by default, so each visit by a user to each page (that hits that clientmanagement="yes") will trigger an update of the client var repository for 2 variables, hitcount and lastvisit, whether you ever use them or not. Really quite a tragic thing, this default, and made all the worse when sites are hit by spiders, robots, and load test tools, as they don't remember the cookie CF sets on each visit, and so they cause creation of a new client variable repository entry--an INSERT, rather than an update--on EVERY request for a CF page. It's something I've blogged about here: http://carehart.org/blog/client/index.cfm/2006/10/4/bots_and_spiders_and_poor_CF_performance (Llet me clarify also that if you go searching for such references to ClientManagement being enabled, be aware that it could also say ClientManagement=yes, or "true", or true, etc. Just search for any reference to ClientManagement at all and eyeball the results.) As for a better default, well, you can set it to NONE, but that will fail if indeed any code does enable ClientManagement. A better option may be "cookie", which puts the client vars on the browser. Just be aware that doing that will in fact cause loss of connection to the variables in the previous location, if in fact anyone was using them. If they're not, then this may solve your problem. Hope it helps. ... View more

Bob, this is just a guess, but what OS are you on? Is it Linux or OSX, perhaps (or something else other than Windows)? The registry is of course a Windows concept, and it may be that something is trying to write to it when it's not there. Perhaps our fellow forum reader Jochem will speak up with his experience on Linux systems. As a guess until then (or someone else does), is this a development or production server? If the former, how about going into the CF Admin page for Client Variables and change it to not use Registry as the default repository. And even if you do not have it set to registry (which is the default when you install, at least on Windows systems), consider also that this merely sets the default if code doesn't override it. You could have code where someone sets clientstorage="registry" (as either a this.scope variable in application.cfc or in cfapplication in application.cfm or some other page.) Worth double-checking. ... View more

xkaliburx, I would recommend you look at other logs, not just the server.log (and I assume you meant that, not cfserver.log). Besides others in the [cf]\logs\ directory, see also those in the [cf]\runtime\logs (or [jrun4]\logs, if using the multiserver/multiple instance mode of CF deployment. Often those other logs have much more info on what's gone wrong. I don't recognize anything from what you've offered, though perhaps someone else here may. ... View more

Joe, I'm pretty sure that unfortunately CF5 was unique in not having any updater or even cumulative hotfix. There was a 4.01, a 4.51, a 6.1, a 7.01/7.02 and even an 8.01, but never any 5.anything. (And sadly it appears they went back and edited the pages on hotfixes, including the CF5 ones, to make reference to possible updaters, which may have led you to ask this question.) And it doesn't appear there was even any cumulative hotfix (CHF), a concept that started only in 7.02 if I recall correctly. That would be just as good a solution for you, but again no cigar it seems. It seems you may have no choice but to install the HFs. It would be nice if you could perhaps only install those hotfixes that you had had previously on the other server, back in CF5 there was not any organized tracking of hotfixes (as there is in at least CF7 and 8, where the CF admin has an interface for applying hotfixes and also shows you what hotfixes you have applied). Not encouraging, but hopefully helpful to understand the dilemma. /charlie ... View more

OK, so in 7.01, you need to upgrade the drivers to get Windows Authentication to work. The drivers that were built-in in 7 were the 3.4 version from Merant/DataDirect. They weren't updated (as a default in the install of CF) until 8,when they were updated to 3.6. The 3.5 drivers added Windows authentication, and you can apply them to a CF 7/7.01/7.02 install. Check out my blog entry: http://carehart.org/blog/client/index.cfm/2006/8/8/jdbc3.5_update If you wonder what version of the drivers you may already be running (in case someone may already have updated the drivers), see this entry: http://www.carehart.org/blog/client/index.cfm/2006/8/8/checking_jdbc_driver_version Or more simply, just try removing the username/password values in the setup for the SQL Server DSN, to see if it works. If not (and assuming it's not complaining about the CF account username not being an authorized user of the DB), then it seems an update of the drivers is in order. See my first blog entry above for more on what the drivers offer, and why Adobe didn't just update the drivers in the 7 updaters and cumulative hot fixes, so that you must apply the update manually. ... View more

Bob, to your question about windows authentication, yes, CF supports it now. May depend on what version you're using, but try just leaving off the username and password entirely when creating a DSN pointing to the SQL Server db. Of course, this means that the account under which CF is running (defaults to System) must be defined in SQL Server to access the database in question. You may find that the System account can, by default. If you've changed the account under which CF runs (typically done in the Windows Services control panel), then you'd need to make sure that account is defined (in SQL Server) to access the database in question. Also, your second comment refers to ODBC. Just to be clear, are you talking here about setting up an "ODBC socket" DSN in CF, or are you choosing "Microsoft SQL Server" as the database type in the the Administrator? ... View more

Jason, do you realize that your 2 sample URLs calling the CFC are the same? It reads as if you intended them to be different URLs (since the second got a different result, the redirection). Also, what happens if you just try to browse the URL without the ?wsdl (which would normally launch the CFC browser, which requires knowing the CF Admin password). If that fails, then perhaps there's some issue that has nothing to do with web services per se. Let us know what you find. ... View more

Glad to help. It can be so tough sorting through all the possibilities when the stuff hits the fan. Glad the thoughts may have helped. Once you do determine the answer, be sure to mark it as such for future readers of the thread. ... View more

Very good news, Jose. Thanks for sharing. Yes, sometimes when trying to solve a problem, it pays to bring things down to the shortest possible demo, so as to eliminate many potential causes of conflict. In this case, the end point was the issue. Sorry that I (or others) didn't recognize that in your first note. I just don't do enough flex to have spotted it immediately. Would have saved you a week. 🙂 Be sure to mark your last reply as the answer, so that future readers can see it right away. 🙂 ... View more

One more thought, Jose, going back to the comment of not too many resources on Flex/CF integration, I realize you may mean something other than fundamentals, and fair enough. But in case you do mean even basics, I'll offer a couple more resources that may help you at least confirm that things should work *at all*. There are also a couple of Adobe TV videos showing Flex/CF integration: http://tv.adobe.com/#vi+f1472v1498 http://tv.adobe.com/#vi+f1472v1517 The first does everything from scratch, in CF and FlexBuilder (18 minutes). The second shows using the Wizard in the Eclipse Extensions for CF (10 minutes). Again, sorry if you're not interested in such basics. Just offering it in case you may have been. ... View more

Jose, you say you can't find much about Flex calling remote objects. Really? There are many, many such resources. But maybe you mean that refer to this badversion error. Doing a little digging, I see references to issues related to SSL/HTTPS. Is that a part of what you're doing? Check out these. http://www.adobeforums.com/webx/.59b4dc44 http://www.nabble.com/SSL-Https-communication-between-swf-and-data-service---life-cycle-is-failed-td18922452.html Here also is an entry where someone writes about calling a CFC from Flex, and in a comment he mentions the badversion error. Though he never mentions resolving it specifically, he seems to have gotten things working, so maybe among the few things discussed is a solution for you. http://www.flashcomguru.com/index.cfm/2006/11/11/flex2remoting I also see one that suggests that the badversion error is just a generic error reflecting another problem in the connection. While it discusses AMFPHP, which is an open alternative to the FlashRemoting built into CF, it may still offer insight: http://www.5etdemi.com/blog/archives/2005/06/i-did-it-i-killed-netconnectioncallbadversion If none of them are it, since it seems maybe you're having difficulty calling ANY CFC component from AIR/Flex, check out any of these examples to see if you can get them to run: http://livedocs.adobe.com/flex/3/html/help.html?content=data_access_4.html http://tutorial519.easycfm.com/ http://www.cftips.net/post.cfm/flex-data-grid-with-coldfusion-flash-remoting-using-cfc Just be careful as you're looking at resources for Flex examples: some are for 1.5, some for 2, some for 3. Hope that helps. ... View more

Al and Tim, while truly understanding the problem may take some effort, have you tried the work around of doing a try/catch on the CFAPPLICATION tag, as listed in the comment in this blog entry: http://www.pjk.us/paul/index.cfm?mode=entry&entry=9603C7B2-3048-28E9-DAD333835BEAFD8A#c9D057530-3048-28E9-DAA2112B8C50D861 It may at least let you avoid the error while you work to better understand it. ... View more

Panda, the URL to use depends on many things. Did you install CF? During the install, did you choose the option to use the built-in web server? Or the external web server (like IIS or Apache)? If the latter, then you wouldn't (typically) specify a port in the URL. Have you tried that? If you installed using the built-in web server, you also would have been asked what port to use. It might be 8500, or if you had another version of CF already installed, you would have been given another port as an option (perhaps 8501). Also, if you installed CF using the multiserver/multiinstance mode, you'd likely have a yet different port (like 8300, or 8301, etc.) There's a way to tell for sure whether you're using the built-in web server and what port. Check the doc discussed here ( http://www.adobe.com/support/coldfusion/adv_development/config_builtin_webserver/config_builtin_webserver03.html) and see if your file shows the deactivated entry as false or true. If false, then it's enabled and available. Check the port entry for the value to use. ... View more

MM, have you looked at other than the [cf]/logs? There are also [cf]/runtime/logs/ which often have far more (and more useful) info for solving serious problems like this. If you're running the multiserver (multi-instance) deployment of CF, then look for them in the [jrun4]/logs/ directory instead. Also, you don't say if you're using CF8 Enterprise or Standard. If the former, you may get value from the CF8 Server Monitor, by enabling "start monitoring" to view what requests are running when things seem to go bad. You may have some hung requests, and the connection error could be from the web server not getting an answer from some pages because they're hung up. I don't use Apache much so can't tell from the error message if that may be an issue. It's just a guess. Let us know what you see. ... View more

Dan, does the query that "takes long sometimes" have CFQUERYPARAM? If so, I'd point out that when you copy the SQL to the DB, you would have to change the SQL to hard-code whatever variable values would have been passed to the CFQUERYPARAM. In doing so, you have really changed the query. I know it doesn't seem to, but you have. Before I elaborate, though, let's hear if you confirm you are indeed using a cfqueryparam. ... View more

Jose, I'm literally about to run out the door to teach a class for 3 days, so can't offer too much help. But whether calling from AIR or Flex it should be the same (about calling a CFC on a CF server). And in that regard, I'll propose that you look for (search for) references to people accessing the admin API from flex. The CF server monitor is itself a Flex app calling those APIs, so it certainly does work. It may be that there are some steps you need to take (and certainly other methods you need to call before the servermonitoring cfc methods, including the login method of the adminstrator.cfc, though I don't think that's the cause of your error above). In fact, the error almost makes me think there's instead some configuration problem (since it refers to "badversion"). I don't do enough Flex to know, and again can't search for it at the moment, but I would focus first on that error, and search for info on that (without mention of the admin api, since the error may not have anything to do with it). In that regard, can you call any other CFCs, besides the admin api, as a test? Just trying to help. Will likely be several hours before I can reply. ... View more

I'm guessing that you're using shared hosting, which means you share the server with many other sites. As such, you will not have access to the CF Admin, and that's why I asked "did you (or someone at GoDaddy) define a datasource in the CF administrator to point to that database". This really isn't a CF problem. This is a problem either of your not having been given fundamental information from your host ("how do I setup a database for use by CF?"). You've got to go to them for this information. We can't help you here (unless a reader happens to be a fellow user of GoDaddy's CF hosting services.) If you can't get help from them, it may be in your interest to move to a host that does support CF more clearly and effectively. I have a link to dozens of CF hosting companies here: http://www.cf411.com/#cfhost ... View more

Chipped, you haven't clarified: did you move the database to the remote server? and did you (or someone at GoDaddy) define a datasource in the CF administrator to point to that database? Those are steps you would have done on your own local server. You simply need to have them do it on the remote one now. There are plenty of other cautions that could be offered: you really ought not be using Access for a production application, though many do. You really ought to put the file into a location on the remote server that is not web-accessible, so that no one can "just download it" if they could figure out the URL to point to it. But to answer your main concerns, I hope the info above helps. ... View more

Well, you have 3 questions here: support for 64 bit, support for Windows Server 2008, and support for CF7. Let's take them one at a time. As for 64-bit, there's an important difference between being able to run on a 64-bit OS and being able to run in 32-bit or 64-bit mode on that 64-bit OS. That said, only CF8 supports running in 64-bit mode. Further, in 8.0 it was only on Solaris, then 8.01 added Windows (including Server 2008 among others), Linux, and Mac. 64-bit mode is also supported only in CF8 Enterprise specifically (not Standard). So you can run CF 8 Standard on a supported 64-bit OS, but only in 32-bit mode. More on 64-bit support at the CF8.01 update FAQs: "Does ColdFusion have 64-bit support?" http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403277&sliceId=1#_Toc193176415 and "Does ColdFusion Standard have 64-bit support?" http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403277&sliceId=1#_Toc193176416 But you said you want to run CF7. Of course, that's not going to allow you to run in 64-bit mode, as discussed above. But you can at least install it on a 64-bit machine as long as it's a supported OS, running CF in in 32-bit mode. More on that at http://www.adobe.com/go/8be22ed6. Sadly, for you, Windows Server 2008 is NOT listed as a supported OS For CF7. More at http://www.adobe.com/products/coldfusion/coldfusion7/systemreqs/. To sumarize, you will need to move up to CF8 to get Win2k8 as a supported OS, then to 8.01 to get 64-bit support, and then only in CF8 Enterprise. /charlie ... View more