ColdFusion MySQL drivers

R

Rossv1

Perch
I've had numerous issues with the MySQL drivers on multiple ColdFusion servers in the past 5 months. I've had to submit numerous tickets and have had significant downtime because of these issues. Even when I advised your tech of the issue during the last outage, it took 2 days for him to realize I was correct and update the MySQL drivers. I currently have two more sites down on CF2 and CF4 for this exact reason.

I'd like to know why these drivers keep changing, and what can be done to prevent this from happening again in the future. I've been a customer for over 7 years, and have never had these issues in this abundance in the past. To be honest, I'm getting tired of submitting the same ticket over and over again.

I do have an current open ticket [RS #IOT-68808-580]

Also, as a side note, many of my tickets do not appear in the cerebus system, and those that do are never closed! ( I have tickets going back to 2006 in the queue, every single one is still marked 'awaiting reply')....
 
Thank you for fixing this. What I don't understand is WHY this keeps happening. I've had to report this exact problem with CF2 a number of times, each time the MySQL connector was incorrect. Once it gets changed, why is someone changing it again? You should never have to update the MySQL drivers for CF once they are in place. I've been a CF server admin for 10 years, so I understand the process quite well.


Can you please put some policy in place to prevent this from reoccurring? As mentioned, I've had significant downtime because of this issue.
 
Rossv1 said:
Thank you for fixing this. What I don't understand is WHY this keeps happening. I've had to report this exact problem with CF2 a number of times, each time the MySQL connector was incorrect. Once it gets changed, why is someone changing it again? You should never have to update the MySQL drivers for CF once they are in place. I've been a CF server admin for 10 years, so I understand the process quite well.


Can you please put some policy in place to prevent this from reoccurring? As mentioned, I've had significant downtime because of this issue.
Click to expand...
Ross,

It happened because the servers moved.

It can also happen if you go to hsphere odbc drivers section, because it is a custom driver for the new mysql, and not in the CP, if you go to the CP ODBC it can reset to old
 
You must log in or register to reply here.
Back
Top