[
https://issues.apache.org/jira/browse/OPENJPA-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706659#action_12706659
]
Michael Dick commented on OPENJPA-1067:
---------------------------------------
Actually on second hand I think there's a separate issue here : whether we
should remove the supportsQueryTimeout field.
Selectively disabling some methods like we are with supportsQueryTimeout is
problematic and it's easy to get out of sync with JDBC vendors (like we did in
this case). We could let the call go through and let the upstream callers
handle the exception - rather than checking for supportsQueryTimeout before
calling the method.
That's not a change I'm comfortable making in 1.2.x or 1.0.x though. Negating
the call and logging could be done though.
There's a fair amount of precedent for checking before calling though (avoiding
the trip to the database). Unless there are objections I'll open a sub-task /
related issue to discuss whether we need the supportsQueryTimeout field.
> 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.
