------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
I am also getting the same problem, however , be it the first or the second Time I keep on getting The above error(Apparent wrong driver)
In my case if I connect Directly using DriverManager.getConnection() , then I am able to connect to the DataBase, but when i try using Connection Pooling i.e ds.xml and then Look up, I get this error. I use following url in ds.xml, <connection-url>jdbc:microsoft:sqlserver://servername:1433;DatabaseName=dbname;User=uname;Password=pwder</connection-url> Plese let me know if this is correct or not. I use following jars 1.msbase.jar 2.mssqlserver.jar 3.msutil.jar
------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
Hi All, My Problem is finally resolved. I switched over to jtds drivers (freeware) . I wasted 3 days trying with Microsoft Drivers and it Took only 5 mins for Connection Pooling using jtds drivers.
------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
I was having the same problem and also switched to jtds, but the problem remains.
My connection is failing randomly with "Apparently wrong driver class specified for URL" error.
The connection will fail this way over and over again, then will randomly begin to work. It's maddening! Is anyone else experiencing this?
I am running JBoss on Java 1.506, conncting to MSSQL with jtds 1.2 with the folloding datasource specifier:
<local-tx-datasource> <jndi-name>MSSQLDS</jndi-name> <connection-url>jdbc:jtds:sqlserver://192.168.100.100:1433/CADB;tds=8.0;lastupdatecount=true</connection-url> <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class> <user-name>username</user-name> pwd <!-- sql to call on an existing pooled connection when it is obtained from pool --> <check-valid-connection-sql>SELECT 1</check-valid-connection-sql> </local-tx-datasource>
Weston.Price@Jboss.Com 4 October 2006 04:11:39 [ permanent link ]
How are you deploying your datasource? Are any of the JDBC jars contained in the lib directory or your WAR? Do any of the JDBC jar files reside in an EAR?
Typically we see this error when a user tries to deploy the jars inside of an application archive and not in the server/server-config/lib directory.
Wow, that was a swift response! Turnaround time of 4 minutes - ought to be in an ad for JBoss....
Indeed, the jar file was being deployed in the WAR module. I removed it from the WAR and put in in the config/lib directory as specified, and it now seems to be working reliably.
Weston.Price@Jboss.Com 4 October 2006 04:46:53 [ permanent link ]
Not a problem
Note, this is a bug in the DriverManager. Basically what is going on is some heinous cacheing of classes that prevents the class from being loaded. Supposedly this is addressed in JDBC 4.0. Also, the Class.forName("classname") mess goes away. The DriverManager will be able to load the classes automatically without the registration process.
![[JCA/JBoss] - Re: NestedSQLException: Apparently wrong driver class specif](http://qaix.com/i/logo_new.gif){kind=logo}
