SQLGrinder 2B5 Connection Failure

[ylon]

I'm trying to use SQLGrinder to log onto a localhost MAMP mysql db and it is not working. I am receiving the following error at the bottom of the window after the connection try: (in red letters) "No suitable driver"

I can log in just fine via `mysql -p -u root` in the shell. phpMyAdmin works great. I can get in just fine with CocoaMySQL-SBG by passing the following socket to it: /Applications/MAMP/tmp/mysql/mysql.sock

However I cannot get SQLGrinder to connect whatever I do. I have changed my java vm link to point back to the 1.4.2 jvm from 5 and then I upgraded my /Library/Java/Extensions mysql driver from mysql-connector-java-3.0.16-ga-bin.jar to mysql-connector-java-3.2.0-alpha-bin.jar.

Please advise as this is quite frustrating.

[michaeldupuis]

[ylon]

Well, I tried to use the default (jdbc:mysql://localhost) without the URL check box checked. Then I tried to place my own URL in there such as:

jdbc:mysql://localhost/mysql?user=test&password=test

and to no avail.

Version of mysql:
mysql Ver 14.7 Distrib 4.1.12, for apple-darwin7.9.0 (powerpc) using EditLine wrapper

(packaged with MAMP)

[michaeldupuis]

Huh, try filling all the information, which might be required. For instance, the URL I used to connect to my mysql databases looks like this:

jdbc:mysql://127.0.0.1:3306/databasename

-- Michael

[ylon]

Still no luck. Any additional log information that SQLGrinder may be keeping that we can dig into?

[michaeldupuis]

Did you enter all of the values into the URL field, into the text fields, or did you try both methods?

[ylon]

Both methods...

[michaeldupuis]

I know this works, because I connect to MySQL all the time, so there must be some configuration issue.

According to the Connector/J documentation, "No suitable driver" can be caused by classes not in the classpath, or a mistaken URL or if there are no drivers specified based on the jdbc.drivers system property.

You haven't mentioned what is listed in "JDBC Drivers" preferences, which I mentioned before. What do you find there for any MySQL entries?

-- Michael

[ylon]

Sorry, did not catch your jdbc driver note, but here is what is therein:

MySQL
org.gjt.mm.mysql.Driver
jdbc:mysql
Enabled
file:/Library/Java/Extensions/mysql-connector-java-3.2.0-alpha-bin.jar

System default extensions directories is checked
SQLGrinder Application Support directory is checked

[michaeldupuis]

Ok, try moving that file out of that folder, or unchecking "System default extensions directories" and restarting the app. You should now see the JDBC driver listed as being in the SQLGrinder.app application package. Try connecting now and see if there is the same issue.

[ylon]

Interesting. I am getting another error now:

Cannot load connection class because of underlying exception:
'java.lang.SecurityException: Prohibited package name: java.sql'.

What do you think of that?

[michaeldupuis]

What's the full stack trace from the message log? You can open the log from the Tools menu.

[ylon]

Sorry, had to be away for the last couple days, here is the log:

java.sql.SQLException: Cannot load connection class because of underlying exception: 'java.lang.SecurityException: Prohibited package name: java.sql'.
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:277)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:172)
at com.advenio.jdbclib.threads.ConnectionThread.threadRunLogic(ConnectionThread.java:52)
at com.advenio.jdbclib.threads.AbstractThread.run(AbstractThread.java:43)

[ylon]

I'm still getting no connection with SQLGrinder with b7. Using the built in driver, Message Log:

Not suitable drive:

java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:532)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.advenio.jdbclib.threads.ConnectionThread.threadRunLogic(ConnectionThread.java:52)
at com.advenio.jdbclib.threads.AbstractThread.run(AbstractThread.java:43)

[michaeldupuis]

Huh, that doesn't look like any of the traces I get from that driver. The new format, and the one that seems to be dumped from the included driver (mysql-connector-java-3.1. connecting to server version 4.0.18 looks like this when I specify the wrong port:

com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:

** BEGIN NESTED EXCEPTION **

java.net.SocketException
MESSAGE: java.net.ConnectException: Connection refused

STACKTRACE:

java.net.SocketException: java.net.ConnectException: Connection refused
at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:151)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:280)
at com.mysql.jdbc.Connection.createNewIO(Connection.java:1774)
at com.mysql.jdbc.Connection.<init>(Connection.java:437)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:268)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.advenio.jdbclib.threads.ConnectionThread.threadRunLogic(ConnectionThread.java:52)
at com.advenio.jdbclib.threads.AbstractThread.run(AbstractThread.java:43)


** END NESTED EXCEPTION **


at com.mysql.jdbc.Connection.createNewIO(Connection.java:1839)
at com.mysql.jdbc.Connection.<init>(Connection.java:437)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:268)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.advenio.jdbclib.threads.ConnectionThread.threadRunLogic(ConnectionThread.java:52)
at com.advenio.jdbclib.threads.AbstractThread.run(AbstractThread.java:43)

I really looks like it's finding another driver somewhere else (note the difference in class names, com.mysql vs. java.sql) and using that, which might cause the problem. I suggest opening preferences again and seeing what MySQL drivers are listed in there. If this doesn't work, I'll give you a simple JDBC app to try, I think this is more a JDBC issue than a SQLGrinder issue.