Last night I upgraded my staging environment to MySQL 4.1.7 from 4.0.20 and found that James 2.2.0 could not get a connection to the database, failing with a

        java.sql.SQLException: Giving up... no connections available.

error message. After simply replacing the mm.mysql-2.0.14.jar in james.sar with the latest Connector/J jar (3.0.15), the problem stopped. So I think it's safe to conclude that mm.mysql-2.0.14.jar is not compatible with MySQL 4.1.7, though it does seem to work fine with MySQL 4.0.20. Has anyone else had this same experience, or could it be that I unknowingly did something else that fixed the problem?

Nathan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to