ClientDriver, have included derbyclient.jar in build path

Asked Sep 10 '18 at 05:06

Active Sep 10 '18 at 05:12

Viewed 54 times

I have encountered this error in eclipse, attempting to connect to my database. I have looked at these suggestions:

SQLException: No suitable driver found for jdbc:derby://localhost:1527

However they all seem to suggest including derbyclient.jar into build path for your project, which I have.

java.lang.NoClassDefFoundError: org/apache/derby/jdbc/ClientDriver at datasource.DBConnection.getDBConnection(DBConnection.java:38)

my database connection:

private static final String DB_CONNECTION = "jdbc:derby://localhost:1527/database;create=true"; 
private static Connection getDBConnection(){
   try {

        DriverManager.registerDriver(new org.apache.derby.jdbc.ClientDriver());

        Connection dbConnection = DriverManager.getConnection(
                        DB_CONNECTION, DB_USER,DB_PASSWORD);
        return dbConnection;

    } catch (SQLException e) {

        System.out.println(e.getMessage());

    }
    System.out.println("Connection problem");
    return null;

}

edited Sep 10 '18 at 05:12

zabop

6,750
3
39
84

asked Sep 10 '18 at 05:06

Callum

needs to be on your classpath when you run it – Scary Wombat Sep 10 '18 at 05:07
Your code should never call `DriverManager.registerDriver`. That method is only to be called by JDBC drivers themselves. – Mark Rotteveel Sep 10 '18 at 08:03
The error means that the jar was present while compiling, but not when executing the application. – Mark Rotteveel Sep 10 '18 at 08:04

java.lang.NoClassDefFoundError: org/apache/derby/jdbc/ClientDriver, have included derbyclient.jar in build path

0 Answers0