MySQL driver error...

I have MySQL 4.1.12. running.

I have the Connector/J 3.1 driver installed.

Driver = “org.gjt.mm.mysql.Driver”
URL = “jdbc:mysql://localhost:3306/database”

I keep getting the below error message.

It is a driver problem I guess because MySQL Administrator works but any application relying on the driver doesn’t…

Anybody any idea why this problem occurs?

java.sql.SQLException: Communication link failure: java.io.IOException, underlying cause: Unexpected end of input stream

** BEGIN NESTED EXCEPTION **

java.io.IOException
MESSAGE: Unexpected end of input stream

STACKTRACE:

java.io.IOException: Unexpected end of input stream
at com.mysql.jdbc.MysqlIO.readPacket(MysqlIO.java:1073)
at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:619)
at com.mysql.jdbc.Connection.createNewIO(Connection.java:1511)
at com.mysql.jdbc.Connection.(Connection.java:485)
at com.mysql.jdbc.Driver.connect(Driver.java:341)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:83)
at com.servoy.j2db.persistence.datasource.n.createConnection(Unknown Source)
at com.servoy.j2db.persistence.datasource.r.makeObject(Unknown Source)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:816)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:110)
at com.servoy.j2db.persistence.datasource.i.getConnection(Unknown Source)
at com.servoy.j2db.persistence.Server.getConnection(Unknown Source)
at com.servoy.j2db.persistence.Server.testConnection(Unknown Source)
at com.servoy.j2db.develop.q$2.run(Unknown Source)
at com.servoy.j2db.util.ap.run(Unknown Source)
at java.lang.Thread.run(Thread.java:613)

** END NESTED EXCEPTION **

OK, solved it. Is a tip for all you mac os users out there (which I ofcourse forgot to mention)…

I have several Servoy installs, all with the same driver. But I also use other applications and that was the source of the problem. It installed a driver under ‘Library/Java/Extensions’. The driver was old but interfered with the newer driver.

After replacing the driver the issue was solved!

Cheers,