Hello,

I am not able to get the sajdbc4 driver to work in my Java EE app. I have tried two cases as described below but each fails with a different error. I had the app workinh with jConnect but need to change to sajdbc4 to allow me to connect to a High Availability/Mirrored system but I can't even get the basic driver working.

Case One - what I thought was the straightforward way to do this: 1) Per Ref 1, the 1st step is to add the driver .jar to the classpath. I used Eclipse to add the driver .jar to the classpath and here is what I see added to the classpath file: <classpathentry kind="lib" path="C:/Program Files/SQL Anywhere 17/Java/sajdbc4.jar"/>

2) Per Ref 2, the support files are confirmed to be in the (Linux) directory (from the SQL Anywhere installation): /opt/sqlanywhere17/lib64

3) We don't need to manually load the driver so the code I'm using is (connection string format is from Ref 3:

final String sConnectionURL = "jdbc:sqlanywhere:Host=<ipaddress>:<port>;ServerName=MyHAAlternateServerName";
try {
    synchronized (DriverManager.class) {
        final Properties props = new Properties();
        props.put("User",ConnectToDatabase.USER_NAME);
        props.put("Password",ConnectToDatabase.PASSWORD);
        connection = DriverManager.getConnection(sConnectionURL,props);
        }
    }
...

This crashes on getConnection() with: 17:17:02,505 ERROR [stderr] (default task-4) java.sql.SQLException: No suitable driver found for jdbc:sqlanywhere:Host=<ipaddress>:<port>;ServerName=MyHAAlternateServerName ... 17:17:02,585 ERROR [io.undertow.request] (default task-4) UT005023: Exception handling request to /OpsServer/run: java.lang.RuntimeException: java.sql.SQLException: No suitable driver found for jdbc:sqlanywhere:Host=<ipaddress>:<port>;ServerName=MyHAAlternateServerName

Case Two - see what happens if we manually load the driver: 1) Same as above.

2) Same as above.

3) We try to manually load the driver 1st as follows:

try {
    // Shouldn't need to manually load driver but we do this to debug.
    DriverManager.registerDriver((Driver)Class.forName("sap.jdbc4.sqlanywhere.IDriver").newInstance());
...

This crashes on registerDriver() with: ERROR [stderr] (default task-3) java.lang.ClassNotFoundException: sap.jdbc4.sqlanywhere.IDriver from [Module "deployment.MyApp.war:main" from Service Module Loader]

What adds to the confusion is that the app runs under the WildFly Java EE app server. I setup a WildFly DataSource (which I am not yet using) and that requires pointing it at the sajdbc4.jar and also supplying a Connection string. I did this and then ran the "Test Connection" that WildFly provides and we get the message "Successfully created JDBC connection." So that suggests to me that at least the sajdbc4.jar and Connection string are correct. Here are some lines from the Eclipse console that reinforce the apparent fact that the WildFly DataSource facility is able to access the driver:

17:13:22,599 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0005: Deploying non-JDBC-compliant driver class sap.jdbc4.sqlanywhere.IDriver (version 4.0)
...
17:13:23,873 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = SybaseSA

What is missing or is incorrect in what I am doing when my app tries to get a connection?

Thank you.