openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (OPENJPA-964) Finish updating sql-error-state- codes.xml for query timeout support on other DBs
Date Wed, 15 Apr 2009 22:17:15 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698918#action_12698918
] 

Donald Woods edited comment on OPENJPA-964 at 4/15/09 3:16 PM:
---------------------------------------------------------------

For Informix - If the SQL request can be interrupted, the database server takes the following
actions:
   1. Discontinues execution of the current SQL request
   2. Sets SQLCODE (sqlca.sqlcode) to a negative value (-213)
   3. Returns control to the application
When the application regains control after an interrupted SQL request, any resources that
are allocated to the SQL statement remain allocated. Any open databases, cursors, and transactions
remain open. Any system-descriptor areas or sqlda structures remain allocated. The application
program is responsible for the graceful termination of the program; it must release resources
and roll back the current transaction.

      was (Author: drwoods):
    Example stand-alone test output for Informix Dynamic Server 11.50 using the IBM Universal
JCC drivers (from DB2 9.5) -
Statement = select * from qtimeout where mod(DELAY(2,id),2)=0
SQL Message = IDS SQL Error: SQLCODE=-674, SQLSTATE=IX000, SQLERRMC=delay, DRIVER=3.50.152
SQL State   = IX000
SQL Code    = -674
Stack trace = com.ibm.db2.jcc.b.SqlException: IDS SQL Error: SQLCODE=-674, SQLSTATE=IX000,
SQLERRMC=delay, DRIVER=3.50.152
	at com.ibm.db2.jcc.b.wc.a(wc.java:55)
	at com.ibm.db2.jcc.b.wc.a(wc.java:126)
	at com.ibm.db2.jcc.b.tk.c(tk.java:1901)
	at com.ibm.db2.jcc.b.tk.d(tk.java:1889)
	at com.ibm.db2.jcc.b.tk.a(tk.java:1416)
	at com.ibm.db2.jcc.t4.db.g(db.java:138)
	at com.ibm.db2.jcc.t4.db.a(db.java:38)
	at com.ibm.db2.jcc.t4.t.a(t.java:32)
	at com.ibm.db2.jcc.t4.sb.h(sb.java:141)
	at com.ibm.db2.jcc.b.tk.N(tk.java:1387)
	at com.ibm.db2.jcc.b.tk.a(tk.java:2215)
	at com.ibm.db2.jcc.b.tk.a(tk.java:557)
	at com.ibm.db2.jcc.b.tk.executeQuery(tk.java:541)
	at DirectQueryTimeoutTest.main(DirectQueryTimeoutTest.java:84)


  
> 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
>
>         Attachments: OPENJPA-964-common.patch, OPENJPA-964-db2.patch, OPENJPA-964-mssql.patch,
OPENJPA-964-oracle.patch
>
>
> 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.


Mime
View raw message