Looks like this code was checked in a year ago by Patrick Linskey with the
comment "Improve concurrency by actively managing AbstractBrokerFactory's
broker set when using non-finalizing brokers. Credit goes to Arunabh
Hazarika for identifying the bottleneck and prototyping this solution."
I'm not
Hi,
I have just completed the first steps with OpenJPA running in my Eclipse
RCP app. I use Derby with the EmbeddedDriver. So far so good.
I have another set of plugins, Eclipse Data Tools Project (DTP), which
provide some DB management tools. However, both OpenJPA and DTP want to own
the Derby
Hi Mike,
I've tracked the problem down to
org.apache.openjpa.kernel.AbstractBrokerFactory. The heap dump lists the
_brokers Set as containing all the references to FinalizingBrokerImpl, and
it appears the assignment of this set was changed to this:
if (FinalizingBrokerImpl.class.isAssignab
JIRA Issue: https://issues.apache.org/jira/browse/OPENJPA-1188
On Tue, Jul 21, 2009 at 8:42 AM, Kevin Sutter wrote:
> For those of you interested, here are the details on this problem and
> what's required to reproduce it. I will be opening a JIRA and posting a
> testcase shortly.
>
> Requirem
For those of you interested, here are the details on this problem and what's
required to reproduce it. I will be opening a JIRA and posting a testcase
shortly.
Requirements...
o Your Entity needs to have an attribute that OpenJPA wrappers with a
proxy. This proxy is used to detect changes to t
I finally worked it out. Took me a few days but I have to set cascade type
on the Role entity to "Refresh" then it will only update the join table and
not attempt to update the entity tables.
Finally!
Chris
From: C N Davies [mailto:c...@cndavies.com]
Sent: Sunday, 19 July 2009 5:14
