openjpa-dev mailing list archives

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


Michael Dick updated OPENJPA-1067:

    Attachment: OPENJPA-1067-round2.diff.txt

For released versions (1.0.x - 1.2.x) I'm leaning towards something like the attached patch
(for 1.2.x). 

In trunk we may want to do something better (ie separate dictionaries for DB2ZOS to make this
a little less kludgy, and as Donald said the code path is a little different so it might need
some tweaking. 

The patch uses jMock in the testcase to simulate a connection to Z so if you just apply it
in an IDE you may need to regen your list of dependencies (mvn eclipse:eclipse, or something

> 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
>         Attachments: OPENJPA-1067-round2.diff.txt
> 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