Topic
1 reply Latest Post - ‏2008-10-22T15:33:40Z by reneriv
reneriv
reneriv
6 Posts
ACCEPTED ANSWER

Pinned topic SqlServer 2005 driver version is not clear on WAS 6.1.0.17

‏2008-10-22T15:25:53Z |
I downloaded sql server driver 1.2 from the MS site.
I added the sqljdbc.jar to a new provider that I created on WAS 6.1.0.17. When the server comes up I get the following details:
10/22/08 11:12:23:064 EDT 0000001d InternalGener I DSRA8203I: Database product name : Microsoft SQL Server
10/22/08 11:12:23:096 EDT 0000001d InternalGener I DSRA8204I: Database product version : 9.00.1399
10/22/08 11:12:23:096 EDT 0000001d InternalGener I DSRA8205I: JDBC driver name : Microsoft SQL Server 2005 JDBC Driver
10/22/08 11:12:23:096 EDT 0000001d InternalGener I DSRA8206I: JDBC driver version : 1.1.1501.101

Then when I run/use the dataSource I get the following:

10/22/08 11:13:52:716 EDT 0000002b DSConfigurati I DSRA8203I: Database product name : Microsoft SQL Server
10/22/08 11:13:52:716 EDT 0000002b DSConfigurati I DSRA8204I: Database product version : 9.00.1399
10/22/08 11:13:52:731 EDT 0000002b DSConfigurati I DSRA8205I: JDBC driver name : Microsoft SQL Server 2005 JDBC Driver
10/22/08 11:13:52:731 EDT 0000002b DSConfigurati I DSRA8206I: JDBC driver version : 1.2.2828.100
10/22/08 11:13:52:747 EDT 0000002b DSConfigurati I DSRA8025I: Successfully connected to DataSource.

My question is why does it say 1.1... at startup and then 1.2. What is it really using? This is misleading and confusing. I need to make sure that the correct version is actually being picked up. My application is getting a weird error where the SQL generated from EJB3 annotations is invalid. I believe it is a persistence.xml config issue and not a jdbc driver, but I am not ruling it out due to the inconsistant messages and the errors I am getting. BTW this application works on JBoss. See the caused by application error below:

Caused by: <openjpa-1.0.3-SNAPSHOT-r420667:646455 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: Invalid column name 'id'. {prepstmnt 1735681908 SELECT t0.id, t0.Version, t0.CreateDate, t0.CreatedBy, t0.Deleted, t0.DomainId, t0.UpdateDate, t0.UpdatedBy, t0.Name FROM Statuses t0 WHERE (t0.Deleted = ?) params=(int) 0} code=207, state=S0001
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:3951)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:97)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:83)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:59)
at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.handleCheckedException(SelectResultObjectProvider.java:155)
at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:40)
at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1223)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:990)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:799)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:769)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:765)
at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:517)
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:238)
at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:277) at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:97)

Any direction on this would be great. Any direction on what might be missing from the persistence.xml would be appreciated as well. I am on a very tight deadline. Thank you in advance.
Updated on 2008-10-22T15:33:40Z at 2008-10-22T15:33:40Z by reneriv
  • reneriv
    reneriv
    6 Posts
    ACCEPTED ANSWER

    Re: SqlServer 2005 driver version is not clear on WAS 6.1.0.17

    ‏2008-10-22T15:33:40Z  in response to reneriv
    Moving to the correct forum. My mistake.
    New location: http://www-128.ibm.com/developerworks/forums/thread.jspa?threadID=230843