[
https://issues.apache.org/jira/browse/OPENJPA-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929296#comment-16929296
]
Gary Shank commented on OPENJPA-2517:
-------------------------------------
Follow-up: I tested using openjpa-all-3.1.0.jar and it seems to be working
fine when I specify javax.persistence.query.timeout=3600 (seconds). My dbinit
(create tables) still fails if I specify it as 3600000 millis. I was hoping to
get some query timeouts by setting javax.persistence.query.timeout=1 but
apparently my database is able to perform all my test queries in less than a
second.
> 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
> Assignee: Heath Thomann
> Priority: Major
> Fix For: 2.2.3, 2.4.1
>
> Attachments: OPENJPA-2517-2.2.x.patch, OPENJPA-2517.patch,
> openjpa-querytimeout-bug.zip, openjpa-querytimeout-working.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
(v8.3.2#803003)
