wincf3 - website takes forever to load

it is not happening for very long, but we are still working with it as well, I woudl be lying to you to tell you it will be solved in 24 hours but I will say we are watching it closely and making changes on DBs as we see them crashing.

happening now :frowning:

I also have a customer on this server who has intermittent issues such that his site, which is completely dynamically DB driven, will stop putting up web pages. It tosses a CF error. Now I realize that CF is possibly the worst server software ever made, as I had personally run CF windows servers for years, so I understand that it’s not really the server’s fault, nor is it Jodo’s fault. However, the customer is getting understandably frustrated. Is my only option to offer him going to be to move to a better web technology like PHP or ASP? Or is there something else we can look into for him?

Thanks,
-Ben

I haven’t seen much of an issue recently except yesterday we had an odd jrun runaway and it would not even kill properly we had to reboot, it was posted in the forum.

Stephen

happening now :frowning:

It definitely seems that Macromedia/Adobe’s inability to code a proper server application is rearing its ugly head again. My customer continues to have their site stop working almost every day. They put in a ticket and in a few minutes it’s working again, but that doesn’t help them from getting very upset. Have you guys gotten any help from Adobe on these continued issues? Are there any patches or anything to help fix these issues where it stops serving up DB calls?

It is getting very hard to keep telling them that we’re looking into it, it’s resolved, but then it keeps happening such that it is not really fixed. Again, I understand it isn’t really JH’s fault, and you guys do a great job. I know how poor of a product CF really is, as I had to run those servers myself for years, and had to deal with this particular customer back then, and for years I told them that the issue isn’t the server itself, but rather CF, and if they switched to PHP or ASP, those issues would likely disappear.

We have the supposed “hotfix” patch applied already :frowning:

My customer continues to see these issues where his site will not load at all. We are trying to find something to show him that it’s the ColdFusion server service that is the cause, in the hopes that he will most his site to something like ASP or PHP. Do you happen to have any good links that show the issues we’re seeing so I can prove it with more than “I’ve seen this for years with CF, it’s an issue of that product”?

guess, you need a “veryhotfix” for this as it still occurs sometime :frowning:

My customer is asking if a support ticket has been opened with Macromedia/Adobe regarding these ongoing issues?

No, and honestly no plan to do so at this point, they will simply suggest to upgrade which isn’t an option with Hsphere.

I have not seen this happen near as much recently either.

this problem still going on here … and looks like it’s going to be here for a very looonggg time :expressionless:

I have several CF sites running very well on Jodohost, with sites on every CF server JH provides. I have not encountered any ODBC errors like those mentioned here in a couple of years. The last time I had such errors was when I had sites using Access. Once I switched them all to MySQL, they ran faster and without all the ODBC errors.

Access sucks as a website database. Let me repeat, ACCESS SUCKS! Properly written CF code and use of a real database (MySql, MSSQL, Oracle, PgSQL, etc.) would probably eliminate or at least greatly reduce the errors your client is encountering.

the problem happens VERY rarely and as Good Oyster said it is much related to access. One doesn’t even have to use access however for it to impact the entire ODBC engine that CF uses and take down others :frowning:

First, I do agree that poor programming and Access contribute to the problem. I ran the servers that hosted this site when I was the system admin for a local ISP. So I know first hand the problems and “solutions” (if you can call them that). I did already force this particular customer to change to a real SQL DB before taking them on as a customer, as I wanted nothing to do with their constant issues from their access DB. But now that it’s on a true DB server, it comes down to CF. I can’t very well tell the customer that it’s his developer’s code, as I have nothing to back it up. The plain fact is, while ColdFusion is a simple yet powerful language, it is probably the worse server service product around today for web hosts (or at least right up there). If it were better, it would be able to put hosts into their own worker process, so at least only 1 site is affected. Alternatively, it could recover from those hangs, but it doesn’t. It is unfortunate, as we do have sites that use it. And it is very tough to justify a customer spending money to redesign their site. The one plus, though, is that they will have this problem regardless of where they go.

The CFODBC is the downfall of all versions of CF as well.

It is a shared component in developer, standard, and enterprise. It is a singular service, enterprise allows a granular control of the working process, but if the ODBC crashes your out of luck :frowning: and a good 95%+ of Cf issues come from ODBC.

here we go again :frowning:

Ticket #KVX-96297-810

Please check domain now.