TechNote

ColdFusion 5 for Linux: Server crashes when using MyODBC driver to connect to a MySQL data source

Issue

Macromedia ColdFusion 5 for Linux may crash when trying to connect to a MySQL data source.

ColdFusion crashes when trying to connect to MySQL data sources using the MyODBC driver provided by MySQL. This problem does not exist with the Merant MySQL Driver delivered with ColdFusion. The following errors are displayed in the ColdFusion server.log file when you encounter this problem:

 "Fatal","12300","07/15/02","14:37:47",,"Caught a fatal signal (11) - Aborting"

This is not a problem with the ColdFusion application server but with the MySQL client when using mySQL 3.23.51, unixODBC 2.2.2, and myODBC 2.50.39. This TechNote describes the code changes you'll need to make to the MySQL client in order to use the MyODBC driver.

Solution

Edit the dbug/dbug.c file on the MySQL client to comment out problem code and prevent this error. You do this by downloading the source tar files, editing the file and compiling the client again:

Download MyODBC, MySQL, and unixODBC source tar files fromwww.mysql.com. You cannot make these changes by installing the RPM.
Run the configure command.
Before running the make command, edit the following file so that it is commented out as shown:

{ edit dbug/dbug.c line 824} /* framep has invalid address during concurrent access, causes segfault: * #ifndef THREAD * if (state->framep != NULL) * state->framep = (char **) *state->framep; * #endif */ { edit}
Compile UnixODBC.
Compile the MyODBC driver.

Note: This TechNote describes problems and how to modify the source code when using mySQL Client 3.23.51, unixODBC 2.2.2, and myODBC 2.50.39. Refer to www.mysql.com for detailed instructions on how to compile MySQL Client, UnixODBC and the MyODBC driver.