First, I want to point out that I was wrong about needing to set a
lock level in code during an optimistic transaction. So actually for
us to run the benchmark, the only necessary setting is:
openjpa.LockManager: pessimistic
Contrary to what Patrick said and I backed up, we don't need to set
This benchmark runs best with a combination of optimistic locking
(most cases) and pessimistic locking (some specific uses identified
explicitly in the code).
Where concurrency is low, an optimistic approach works well. In
specific cases, optimistic results in bad performance due to the
> Sent: Tuesday, February 13, 2007 10:59 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: pessimistic locking
>
> We'd also have to set the LockManager property to pessimistic to get
> database locks. And just to build on what Patrick is saying:
> O
We'd also have to set the LockManager property to pessimistic to get
database locks. And just to build on what Patrick is saying: OpenJPA
can do locking within optimistic transactions on individual
instances, but you have to set a lock level on the FetchPlan in code,
which I don't think we
o:[EMAIL PROTECTED]
> Sent: Tuesday, February 13, 2007 10:22 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: pessimistic locking
>
> Patrick,
> Just to clarify... If we set up OpenJPA in this manner
> (Optimistic to false
> and the Read and Write Lock levels to Non
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 12, 2007 1:51 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Fwd: pessimistic locking
>
> Comments from the experts here?
>
> Craig
>
>
> Begin forwarded message:
>
>
> From: Scott O
ebruary 12, 2007 1:51 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Fwd: pessimistic locking
>
> Comments from the experts here?
>
> Craig
>
>
> Begin forwarded message:
>
>
> From: Scott Oaks <[EMAIL PROTECTED]>
>
Comments from the experts here?
Craig
Begin forwarded message:
From: Scott Oaks <[EMAIL PROTECTED]>
Date: February 12, 2007 11:45:52 AM PST
To: [EMAIL PROTECTED]
Subject: pessimistic locking
Reply-To: [EMAIL PROTECTED]
The SPEC organization is in the process of developing a JPA
I think you also want to set "openjpa.Optimistic" to "false". That
will default to non-optimistic transactions.
Setting the other properties ("openjpa.LockManager",
"openjpa.ReadLockLevel", "openjpa.WriteLockLevel") are probably
unnecessary.
On Jan 12, 2007, at 11:56 AM, Ritika Mahesh
I have the following properties defined in my persistence.xml
Even then the sql for the query
em.createQuery("select object(o) from Neworders o where
o.no_w_id=:warehouseId and o.no_d_id=:districtId ")
does not have the With RS USE AND KEEP UPDATE LOCKS.
However if I make the followi
10 matches
Mail list logo
