[
https://issues.apache.org/jira/browse/OPENJPA-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706559#action_12706559
]
Donald Woods commented on OPENJPA-1067:
---------------------------------------
OK, but should we disable query timeout support for all DB2 zOS users, or just
catch and log any exceptions when calling setQueryTimeout(), which could be
useful for other drivers too. By disabling query timeout support, you also
disable the current lock timeout support which relies on using
setQueryTimeout().
> 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.
