[
https://issues.apache.org/jira/browse/OPENJPA-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heath Thomann updated OPENJPA-2517:
-----------------------------------
Attachment: OPENJPA-2517-2.2.x.patch
HI! I'm attaching a test fix which will allow a user to set a property (I've
chosen openjpa.jdbc.DBDictionary.allowQueryTimeoutOnFindUpdate) which when set
will apply the javax.persistence.query.timeout, in milliseconds, to
EntityManager operations. As I explained in my previous post, today the
query.timeout is applied to EM operations in seconds. Please review and
provide feedback.
Thanks,
Heath Thomann
> 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
> 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
(v6.3.4#6332)
