openjpa-dev mailing list archives

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


Michael Dick commented on OPENJPA-1067:

It's a bit of a tradeoff. We know this call will at best have no effect, and at worst throws
an exception. Either way we've wasted a trip to the database. 

I think in a perfect world it'd be better to have the functions that rely on query timeouts
check whether the DBDictionary supports them and provide feedback (exception or log) when
they're called. That might be more trouble than it's worth though - I haven't looked at the
affected code.  

Before I saw your comment I went ahead and disabled it. I don't think there's any harm in
leaving that code in and leaving the JIRA open though.

> 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