You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2009/05/06 18:17:30 UTC
[jira] Commented: (OPENJPA-1067) SetQueryTimeout(x) where x != 0
causes SQLException with DB2 on Z/OS
[ https://issues.apache.org/jira/browse/OPENJPA-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706481#action_12706481 ]
Donald Woods commented on OPENJPA-1067:
---------------------------------------
Interesting... do you want me to look at this, given I modified how setQueryTimeout() is called in trunk to support the new javax.persistence.query.timeout hint?
> 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.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.