Apache
/
openjpa
mirror of https://github.com/apache/openjpa.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

OPENJPA-1604: Doc update. 

git-svn-id: https://svn.apache.org/repos/asf/openjpa/branches/2.0.x@936440 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Richard G. Curtis 2010-04-21 18:54:35 +00:00
parent 26bd0a50c8
commit e42f17fa48
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
openjpa-project/src/doc/manual/ref_guide_runtime.xml
View File

@ -936,6 +936,24 @@ state in question to circumvent the database limitations that prevent OpenJPA
from issuing a locking SELECT in the first place.
</para>
</listitem>
<listitem>
<para>
When using the pessimistic lock manager and named queries you will see the following
<literal>WARNING</literal> message logged if you do not specify a lockMode on the named query
or you explicitly set it to <literal>LockModeType.NONE</literal>. When using the pessimistic
lock manager a <literal>LockModeType.NONE</literal> will always be promoted to <literal>LockModeType.READ</literal>.
<programlisting>
WARN [main] openjpa.MetaData - Encountered a read lock level less than LockModeType.READ when processing the NamedQuery annotation "findEmployeeById" in class "org.apache.openjpa.persistence.lockmgr.LockEmployee". Setting query lock level to LockModeType.READ.
</programlisting>
If you are using the pessimistic lock manager and you truly do want to set the lock mode to NONE for a
given query, you can use a fetch plan to do so.
<programlisting>
OpenJPAQuery q = em.createNamedQuery("findEmployeeById");
FetchPlan fp = q.getFetchPlan();
fp.setReadLockMode(LockModeType.NONE);
</programlisting>
</para>
</listitem>
</itemizedlist>
</section>
</section>