Bug #16102 "No suitable driver" only with nighly builds
Submitted: 30 Dec 2005 16:52 Modified: 31 Mar 2014 10:39
Reporter: Ken Johanson Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / J Severity:S3 (Non-critical)
Version:nightly 2005-12-30 OS:Windows (win32)
Assigned to: Alexander Soklakov CPU Architecture:Any

[30 Dec 2005 16:52] Ken Johanson 
Description:
Trying nighly builds from

http://downloads.mysql.com/snapshots/mysql-connector-java-3.0/

Jar file is placed in <JRE>/lib/ext, in place of old mysql-j jar(s) that worked okay. 

DriverManager reports: "No suitable driver"

How to repeat:
Remove existing mysql-j jar file from lib/ext (or course), and place nighly jar there. Try and load via DriverManager.
[4 Jan 2006 22:28] Vasily Kishkin 
Sorry...I was not able to reproduce the bug on "nightly 2006-01-04". Could you please re-verify the bug on latest build ?
[5 Feb 2006 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[31 Mar 2014 10:39] Alexander Soklakov 
I close this report as "Can't repeat" because there is no feedback for a long time and codebase is too old. Please, feel free to reopen it if the problem still exists in current driver.