openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-1067) SetQueryTimeout(x) where x != 0 causes SQLException with DB2 on Z/OS
Date Wed, 06 May 2009 18:50:30 GMT

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

Michael Dick commented on OPENJPA-1067:
---------------------------------------

Hi Donald, I appreciate the offer. My proposed solution is to set supportsQueryTimeout = false
for Z/OS in the DB2Dictionary. Preliminary testing works with 1.2.1. 

I don't think it pays to invent something new that handles the value of 0. If that's the only
value it accepts presumably that's the default anyway. 

> SetQueryTimeout(x) where x != 0 causes SQLException with DB2 on Z/OS
> --------------------------------------------------------------------
>
>                 Key: OPENJPA-1067
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1067
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 1.0.3, 1.2.1, 1.3.0, 2.0.0
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>            Priority: Minor
>             Fix For: 1.0.4, 1.2.2, 1.3.0, 2.0.0
>
>
> A recent (AFAIK) update to the DB2 JDBC driver changed behavior when the setQueryTimeout
method is called on a connection to Z/OS and the timeout was non 0. 
> A non zero value is not supported, but previously the value was ignored. Now an SQLException
is raised. 

-- 
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