SQL Server - Microsoft Driver

[diathesis]

Has anyone made use of the new Microsoft SQL Server JDBC driver w/ JBoss? I gave it a shot, and had problems. Rather than work extensively to figure it out, considering I'm relatively new to JBoss, I thought I'd see if anyone else had luck.

I put this in JBoss.jcml:

 <mbean code="org.jboss.jdbc.JdbcProvider" name="DefaultDomain:service=JdbcProvider">
 <attribute name="Drivers">
 org.hsql.jdbcDriver,org.enhydra.instantdb.jdbc.idbDriver,com.microsoft.jdbc.sqlserver.SQLServerDriver
 </attribute>
 </mbean>

 <mbean code="org.jboss.jdbc.XADataSourceLoader" name="DefaultDomain:service=XADataSource,name=dbVoicenet">
 <attribute name="DataSourceClass">com.microsoft.jdbcx.sqlserver.SQLServerDataSource</attribute>
 <attribute name="PoolName">dbVoicenet</attribute>
 <attribute name="Properties">ServerName=panthro;PortNumber=1433;DatabaseName=dbVoicenetDevGeoff</attribute>
 <attribute name="JDBCUser">voicenetUser</attribute>
 <attribute name="Password">xporbust</attribute>
 </mbean>

And I got this response:

java.lang.ClassCastException:
com.microsoft.jdbcx.sqlserver.SQLServerDataSource
 at
org.jboss.jdbc.XADataSourceLoader.startService(XADataSourceLoader.jav
a:345)
 at
org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:107
)
 at java.lang.reflect.Method.invoke(Native Method)
 at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16
28)
 at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
 at
org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(Conf
igurationService.java:836)
 at $Proxy0.start(Unknown Source)
 at org.jboss.util.ServiceControl.start(ServiceControl.java:81)
 at java.lang.reflect.Method.invoke(Native Method)
 at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16
28)
 at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
 at org.jboss.Main.<init>(Main.java:210)
 at org.jboss.Main$1.run(Main.java:116)
 at java.security.AccessController.doPrivileged(Native Method)

[p_d_austin]

JBoss does not use the datasource from the driver, instead it uses it's own datasource that has a wrapper around a connection from the venodors driver. So what you need to do is put the name of the driver class not the datasource class. See below.

com.microsoft.jdbc.sqlserver.SQLServerDriver

This should fix that problem,
Paul

[davidjencks]

I don't think this is quite right.

Is this MS driver xa capable?

--no-- then you need to use the jboss "fake xa wrapper"
org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl

and specify the MS driver in the jdbc part of the db url. You will need the url.

--yes-- then what you have should work.

I think the class cast exception comes from trying to cast a DataSource to a XADataSource.

[diathesis]

Thanks, that worked, although I now have another problem, the same one that I had under Merant. Started a new thread for that one.

Wondered if the 'XA' part was important -- clearly it is.

[hleblanc]

Where does one get the new Microsoft jdbc driver? Just searched their knowledge base & downloads screen at www.microsoft.com, no luck. Just searched jdbc drivers at java.sun.com, no luck. Is it a freebie?
Thanks!

[diathesis]

http://www.microsoft.com/sql/downloads/default.asp

Should be front and centre, when you get there.

[chjxxx]

I'm having a Message like "[MERANT][SQLServer JDBC Driver]The specified SQL type is not supported by this driver. Any idea?

[dshsapp]

Hi diathesis, can you share the configuration for the following, I am having similar problem trying to use com.microsoft.jdbcx.sqlserver.SQLServerDataSource

getting classcast exception.

thanks

[davidjencks]

See my previous reply in this thread under "no"

[craigday]

watch out for this driver, in out initial tests we ran into a problem where every logical connection we had to the database resulted in 5 physical connections!!!! rediculous. why is this a problem? well eventually you will run into file descriptor limitations on many OSs. there is a related bug in the native oracle driver, you cant open up connections if you have more than 256 file descriptors open.

c