openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1067) SetQueryTimeout(x) where x != 0 causes SQLException with DB2 on Z/OS
Date Thu, 07 May 2009 12:54:31 GMT


Donald Woods commented on OPENJPA-1067:

We have existing code and tests that check for (supportsQueryTimeout == true) today (like
the reworked setTimeouts and setQueryTimeout in DBDictionary in trunk)  so there would be
some minor rework.  Adding a try/catch/log wrapper to any setQueryTiemout() calls along with
always calling getQueryTimeout() before setting a value, would probably be the better route
for 1.3/2.0.  I'd expect DB2 to fix this in the next driver release, given this is a regression/loss
of function for existing users...

> SetQueryTimeout(x) where x != 0 causes SQLException with DB2 on Z/OS
> --------------------------------------------------------------------
>                 Key: OPENJPA-1067
>                 URL:
>             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.

View raw message