[
https://issues.apache.org/jira/browse/OPENJPA-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680251#action_12680251
]
Donald Woods commented on OPENJPA-957:
--------------------------------------
Looks like the existing implementation (not defined in JPA 1.0 Spec and OpenJPA
specific) is using setQueryTimeout() in PessimisticLockManager, which is a
client side JDBC timeout function, while lock timeouts are implemented in the
DB server. See -
DB2 -
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r0011874.htm
MS SQL - http://msdn.microsoft.com/en-us/library/aa213032(SQL.80).aspx
Derby - config property -
http://db.apache.org/derby/docs/dev/devguide/cdevconcepts16400.html
Oracle - LOCKWAIT on the connection or on the DB
Also, the following discussion gives a good overview of the two and why apps
should use both to handle unreliable network conditions -
http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/95755534-bbef-4c2c-afa4-b80ca2a2c333/
> Support lock timeout hint on applicable methods
> -----------------------------------------------
>
> Key: OPENJPA-957
> URL: https://issues.apache.org/jira/browse/OPENJPA-957
> Project: OpenJPA
> Issue Type: Sub-task
> Components: jpa
> Affects Versions: 2.0.0
> Reporter: Jeremy Bauer
>
> This task is to provide support for the lock timeout hint on applicable
> interface methods. OpenJPA currently supports the openjpa.LockTimeout
> property. This support will be extended to allow more granular configuration
> at the method level, where applicable. The pattern used for specifying lock
> modes at a method level should be considered for extension or as a guide.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
