It seems to be to do with using ODBC drivers instead of JDBC drivers, however changing over to JDBC is going to be a huge programming and an even bigger testing task.
We've since been advised that using an ODBC connection to a db is not recommended in a production environment.
Yeah, I'd point to this as a possible cause... CFMX uses a JDBC-ODBC bridge because ODBC is no longer a native option (now that CFMX is a Java application).
I'm surprised it would be a "huge programming [...] task" to switch to JDBC... surely all you need to do is install the Informix JDBC drivers and redefine the data sources? Or am I missing some critical piece of the puzzle? Yes, it would mean retesting everything.
Database queries start to take longer to process.
Additional requests for db queries increase query response times.
eg. a very simple query that normally takes 31ms, goes up to 450ms, then 995ms then over 10,000ms over the space of 10 to 20 minutes. Some longer queries _never_ return results.
Do you have "Maintain Connections" enabled in the "Advanced" settings for the data sources? If so, try turning it off. Once that is off, you can set a timeout to prevent connections taking a long time to complete - that should at least prevent the server from dying. You can also limit the number of connections so that your database doesn't bog down. I'm not saying it *will* fix things but it *may* help...
Regards, Sean
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
