Forum Discussion

apu's avatar
apu
Occasional Contributor
5 years ago

jdbc error getting response for myTeststep; null

I've tried to connect to a Cassandra-DB with the following driver: com.dbschema.CassandraJdbcDriver https://github.com/DataGrip/cassandra-jdbc-driver   After configured the JDBC-Request Step and ...
  • apu's avatar
    apu
    5 years ago

    I have solved my problem. Because of trying difference jdbc-drivers, there was a wrong jar-file version.

     

    Using my java-code in a groovy step, it has returned a Class-not-found-exception. Then I checked the jars and found a wrong version. The jdbc-driver expected a newer version of the cassandra-driver-core. On trying an earlier jdbc-driver, there was an older version in the lib directory.

     

    Why is this exception not thrown in the normal JDBC-Request-Step?

     

     

apu's avatar
apu
Occasional Contributor

Oh, I missed to show my sql-query in Ready-API, but it is the same as in the java code.

 

import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;

public class Test {

	public static void main(String[] args) throws InstantiationException, IllegalAccessException, ClassNotFoundException, SQLException {
		
	String url = "jdbc:cassandra://localhost:9042/mykeyspace?user=myusername&password=mypassword";
	       
        DriverManager.getDriver(url);
        Connection con = DriverManager.getConnection(url);
        
        Statement stmt = con.createStatement();
        ResultSet rs = stmt.executeQuery("select * from mykeyspace.mytable limit 5;");

        while (rs.next())
        	System.out.println(rs.getString(1));        
        
        rs.close();
        stmt.close();
        con.close();

	}
}
apu's avatar
apu
Occasional Contributor
5 years ago

I have solved my problem. Because of trying difference jdbc-drivers, there was a wrong jar-file version.

 

Using my java-code in a groovy step, it has returned a Class-not-found-exception. Then I checked the jars and found a wrong version. The jdbc-driver expected a newer version of the cassandra-driver-core. On trying an earlier jdbc-driver, there was an older version in the lib directory.

 

Why is this exception not thrown in the normal JDBC-Request-Step?

 

 

Recent Discussions