The JDBC driver for SQL Server that comes bundled with JRun 3.1 server, (I believe that the OEM the driver from Merant), can lock up the connection pooler in JRun if SQL Server encounters malformed SQL statements.
The JDBC driver will report an error stating "Un recognized token" when the malformed SQL statement is run against the data base. Following attempts to use the pooled connection report an error stating "Cannot use cloned connection ...." Turning connection pooling off for that defined DataSource alleviates the errors, but then connection pooling is never used, and slower performance results. We have replaced the JDBC driver with a trial product called JTurbo and everything is fine. So we are confident that it is the JDBC driver bundled with JRun server that is the cause of the problem. Does any know how to resolve this problem or if Allaire has a fix. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
