I updated my Branch_3_0 workspace today, rebuilt and found that code that 
worked yesterday stopped functioning today.  Looks like the change to LMCF to 
use DriverManager is now having trouble finding my jdbc driver 
(oracle.jbdc.driver.OracleDriver).

Below is the trace with the SQLException omitted:

<snip>
Caused by: org.jboss.resource.ResourceException: Could not create connection; 
- nested throwable: (java.sql.SQLException: No suitable driver)
        at 
org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:132)
        at 
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnection(InternalManagedConnectionPool.java:236)
        at 
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:101)
        at 
org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:312)
        at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:440)
        at 
org.jboss.resource.connectionmanager.LocalTxConnectionManager.getManagedConnection(LocalTxConnectionManager.java:221)
        at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:504)
        at 
org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnection(LocalDataSource.java:101)
        ... 40 more
Caused by: java.sql.SQLException: No suitable driver
        at java.sql.DriverManager.getConnection(DriverManager.java:532)
        at java.sql.DriverManager.getConnection(DriverManager.java:140)
        at 
org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:116)
        ... 47 more
</snip>

I did not change my config for the datasource at all... I am guessing that the 
LMCF thinks the driver is valid (found the class), since checkDriver did not 
barf, but instead DriverManager did.

VM version info:

<snip>
12:48:35,693 INFO  [ServerInfo] Java version: 1.4.0,Sun Microsystems Inc.
12:48:35,694 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Server VM 
1.4.0-b92,Sun Microsystems Inc.
12:48:35,694 INFO  [ServerInfo] OS-System: Linux 2.4.18-4,i386
</snip>

So, assuming there is not a change to the config (I am using a modified 
oracle-service.xml from the jca examples)... how do I get DriverManager to be 
happy with my driver?

--jason

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to