openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <>
Subject [jira] Commented: (OPENJPA-957) Support lock timeout hint on applicable methods
Date Mon, 09 Mar 2009 20:01:50 GMT


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 -
Derby - config property -
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 -

> Support lock timeout hint on applicable methods
> -----------------------------------------------
>                 Key: OPENJPA-957
>                 URL:
>             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.

View raw message