3 Replies Latest reply on May 20, 2002 11:58 PM by Greg Turner

    Possible Bug in JBoss 3.0.0RC2 JCA ?

    Greg Turner Apprentice

      I use a Cloudscape db. In upgrading my app from JBoss 2.4.4 to JBoss 3.0.0RC2, I discovered by stepping thru the code in my debugger that during startup in LocalManagedConnectionFactory.createManagedConnection
      Connection con = getDriver().connect(internalGetConnectionURL(), new Properties(props));
      returned a null Connection, inspite of it using the same url as was used in 2.4.4.

      I wrote a simple client program to connect to the database in the same way that JBoss 3.0.0RC2 does and verified that the Connection was not being gotten.

      Class c = Class.forName("COM.cloudscape.core.RmiJdbcDriver");
      Driver d = (Driver)c.newInstance();
      Connection conn = d.connect(url, props);

      I then noticed that my JDBC book implies that the proper way to get the Driver explicitly is to do it this way:

      Class.forName ("COM.cloudscape.core.RmiJdbcDriver").newInstance();
      Driver d = DriverManager.getDriver (url);
      Connection conn = d.connect(url, props);

      And my client program verified that this way worked.

      So I am wondering if this is a bug in LocalManagedConnectionFactory or perhaps not if no one else has had this problem.