0 Replies Latest reply on Sep 13, 2011 12:32 PM by fredcurry

SQL Server 2005 Connection Issues

fredcurry Sep 13, 2011 12:32 PM

Can anyone direct me to the correct SQL Server JDBC driver to use? I have tried versions 1.2, 2.0, and 3.0 from Microsoft, but they throw a series of errors.

I have copied the configuration into my *-ds.xml files from http://docs.jboss.org/jbossas/docs/Installation_And_Getting_Started_Guide/5/html/Using_other_Databases.html#d0e3898, and put the driver jar file in my server/server-name/lib folder. When I start my server, I get the below stack trace.

I changed my configuration to use the JTDS driver, but do not want to use this long-term, as it is not supported. Using the JTDS driver also took about 40 minutes to start my server (MySQL takes about 4).

Thanks for any help,

Fred

Stack Trace:

09:39:25,376 INFO [TomcatDeployment] deploy, ctxPath=/starter

09:39:25,433 INFO [RootContainer] Trying to create the portal container 'bres'

09:39:30,981 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null

org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Apparently wrong driver class specified for URL: class: com.microsoft.sqlserver.jdbc.SQLServerDriver, url: jdbc:microsoft:sqlserver://WIN32APP01:1433;DatabaseName=bres_jcr)

at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:225)

at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:195)

at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:639)

at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:273)

at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:690)

at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)

at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:381)

at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)

at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)

at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)

at org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister.openConnection(JDBCConfigurationPersister.java:201)

at org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister.init(JDBCConfigurationPersister.java:132)

at org.exoplatform.services.jcr.impl.config.RepositoryServiceConfigurationImpl.<init>(RepositoryServiceConfigurationImpl.java:89)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

at org.exoplatform.container.ExoContainer.createComponent(ExoContainer.java:321)

at org.exoplatform.container.jmx.MX4JComponentAdapter.getComponentInstance(MX4JComponentAdapter.java:94)

at org.exoplatform.container.management.ManageableComponentAdapter.getComponentInstance(ManageableComponentAdapter.java:68)

at org.exoplatform.container.ConcurrentPicoContainer.getInstance(ConcurrentPicoContainer.java:400)

at org.exoplatform.container.ConcurrentPicoContainer.getComponentInstanceOfType(ConcurrentPicoContainer.java:389)

at org.exoplatform.container.CachingContainer.getComponentInstanceOfType(CachingContainer.java:139)

at org.exoplatform.container.ExoContainer.createComponent(ExoContainer.java:311)