[
https://issues.apache.org/jira/browse/OPENJPA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696718#action_12696718
]
Donald Woods commented on OPENJPA-964:
--------------------------------------
Example output when using MSSQLSimpleDataSourceExample against MS SQL 2005 SP1 -
Statement = update OPENJPA.dbo.QTimeout set versionField = 2 where id = 1
SQL Message = The query has timed out.
SQL State =
SQL Code = 0
Stack trace = com.microsoft.sqlserver.jdbc.SQLServerException: The query has
timed out.
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeInterruptException(Unknown
Source)
at com.microsoft.sqlserver.jdbc.TDSCommand.interrupt(Unknown Source)
at com.microsoft.sqlserver.jdbc.TimeoutTimer.run(Unknown Source)
at java.lang.Thread.run(Thread.java:613)
NOTE: There are no valid SQL State or Error Code being returned from the MS
SQL 2000/2005 JDBC v1.2 driver.
> Finish updating sql-error-state- codes.xml for query timeout support on other
> DBs
> ---------------------------------------------------------------------------------
>
> Key: OPENJPA-964
> URL: https://issues.apache.org/jira/browse/OPENJPA-964
> Project: OpenJPA
> Issue Type: Sub-task
> Components: query
> Affects Versions: 2.0.0
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0
>
>
> Need to add any SQLStatus codes for query timeouts to sql-error-state-
> codes.xml and handle setting isRecoverable/isFatal in each DBDictionary
> subclass for other supported DBs besides Derby and DB2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
