openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-2517) Incorrect the time unit of query timeout value.
Date Wed, 23 Jul 2014 14:58:39 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071814#comment-14071814
] 

Kevin Sutter commented on OPENJPA-2517:
---------------------------------------

Just to be clear...  We would change the OpenJPA default processing to be compliant with the
spec, and introduce the compatibility switch to use the wrong behavior.  I'm sure Rick understood
that approach, but I wanted to be clear in the JIRA.

> Incorrect the time unit of query timeout value.
> -----------------------------------------------
>
>                 Key: OPENJPA-2517
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2517
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 2.2.0, 2.2.1, 2.2.2, 2.3.0
>            Reporter: Masafumi Koba
>         Attachments: OPENJPA-2517.patch, openjpa-querytimeout-bug.zip
>
>
> The value of the "javax.persistence.query.timeout" property have been passed to the java.sql.Statement.setQueryTimeout(int)
in milliseconds rather than seconds.
> The query timeout milliseconds should be converted to seconds.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message