You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Simone Gianni (JIRA)" <ji...@apache.org> on 2009/10/23 15:04:59 UTC
[jira] Created: (OPENJPA-1359) SQLServer driver 2.0 works, but
causes exception in SQLServerDictionary on the first connection
SQLServer driver 2.0 works, but causes exception in SQLServerDictionary on the first connection
-----------------------------------------------------------------------------------------------
Key: OPENJPA-1359
URL: https://issues.apache.org/jira/browse/OPENJPA-1359
Project: OpenJPA
Issue Type: Bug
Components: jdbc
Affects Versions: 1.2.1, 1.2.0
Reporter: Simone Gianni
The driver itself works with OpenJPA, except that the first time OpenJPA tries to obtain a connection it fails with the following exception :
Caused by: java.lang.NumberFormatException: For input string: "JDBC"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.parseInt(Integer.java:497)
at org.apache.openjpa.jdbc.sql.SQLServerDictionary.connectedConfiguration(SQLServerDictionary.java:92)
at org.apache.openjpa.jdbc.sql.DBDictionary.decorate(DBDictionary.java:4157)
at org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:100)
It seems like this method is trying to determine the diver vendor and database version, but fails with vendor/platform informations returned by this driver.
I'm using sqljdbc4.jar and the url in the format jdbc:sqlserver:// .
Despite the "then works" part, this initial exception seriously impairs OpenJPA usage with SQLServer in some scnarios, cause it often gets in the way of the initial schema analysis.
This has been solved in trunk, the patch could be quite simply backported to fix it in 1.2.2 .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-1359) SQLServer driver 2.0 works, but
causes exception in SQLServerDictionary on the first connection
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods resolved OPENJPA-1359.
-----------------------------------
Resolution: Duplicate
Fix Version/s: 1.2.2
Assignee: Donald Woods
Already fixed in 1.2.x branch (1.2.2-SNAPSHOT) by Mike. Try using one of the nightly 1.2.2 builds to confirm the fix.
------------------------------------------------------------------------
r792241 | mikedd | 2009-07-08 13:47:24 -0400 (Wed, 08 Jul 2009) | 7 lines
OPENJPA-1029:
Update SQLServerDictionary to handle Microsoft JDBC Driver.
Merging changes made to trunk in revision 765841.
> SQLServer driver 2.0 works, but causes exception in SQLServerDictionary on the first connection
> -----------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1359
> URL: https://issues.apache.org/jira/browse/OPENJPA-1359
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.2.0, 1.2.1
> Reporter: Simone Gianni
> Assignee: Donald Woods
> Fix For: 1.2.2
>
>
> The driver itself works with OpenJPA, except that the first time OpenJPA tries to obtain a connection it fails with the following exception :
> Caused by: java.lang.NumberFormatException: For input string: "JDBC"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Integer.parseInt(Integer.java:447)
> at java.lang.Integer.parseInt(Integer.java:497)
> at org.apache.openjpa.jdbc.sql.SQLServerDictionary.connectedConfiguration(SQLServerDictionary.java:92)
> at org.apache.openjpa.jdbc.sql.DBDictionary.decorate(DBDictionary.java:4157)
> at org.apache.openjpa.lib.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:100)
> It seems like this method is trying to determine the diver vendor and database version, but fails with vendor/platform informations returned by this driver.
> I'm using sqljdbc4.jar and the url in the format jdbc:sqlserver:// .
> Despite the "then works" part, this initial exception seriously impairs OpenJPA usage with SQLServer in some scnarios, cause it often gets in the way of the initial schema analysis.
> This has been solved in trunk, the patch could be quite simply backported to fix it in 1.2.2 .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.