[
https://issues.apache.org/jira/browse/OPENJPA-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927888#comment-16927888
]
Gary Shank commented on OPENJPA-2517:
-------------------------------------
This so-called "fix" is not working for me. I'm using openjpa-all-2.4.3.jar and
if I specify javax.persistence.query.timeout as 3600000 milliseconds (1 hr), my
dbinit fails just creating the tables due to timeouts. If I specify the timeout
as 3600 seconds (1hr), the dbinit works but other of my regression tests fail
with timeouts. If I specify the timeout as seconds AND specify
openjpa.jdbc.DBDictionary.allowQueryTimeoutOnFindUpdate=true, the dbinit works
but regression tests still fail with timeouts. I also tried setting the
timeout = 1000 with the allowQueryTimeoutOnFindUpdate=true and still no luck.
I'm going to using openjpa-all-3.1.0.jar next but I'm predicting the same
results. All we want is to set the query timeout. I know 1hr seems
ridiculously long but there is a reason for that but even shorter times don't
work so it doesn't seem to matter what I set it as. Please HELP! Thanks.
> 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)
