openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <>
Subject [jira] Commented: (OPENJPA-115) Bottleneck(s) with using OpenJPA in a Container-managed environment
Date Tue, 30 Jan 2007 17:48:33 GMT


Patrick Linskey commented on OPENJPA-115:

> Our original experimentation showed that even with the weak references 
> in ReferenceHashSet, we still bogged down during the cleanup of the 
> _brokers collection.

But that should only be happening when the EMF is closed, right? Presumably, that corresponds
to appserver shutdown / application undeploy. Is your test measuring that part of the application

> Bottleneck(s) with using OpenJPA in a Container-managed environment
> -------------------------------------------------------------------
>                 Key: OPENJPA-115
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>            Reporter: Kevin Sutter
>         Assigned To: Kevin Sutter
>            Priority: Critical
> Running some benchmarks against OpenJPA using the Sun Java System (SunOne) application
server.  Under load, we're not able to push the cpu to 100%.  The culprit seems to be the
lock and synchronization processing within AbstractBrokerFactory.newBroker(..).  According
to sections 5.9.1 and 5.9.2 in the JPA specification, it looks like OpenJPA is attempting
to do too much management of the created EntityManagers.  Within a Container-managed environment,
the Container takes care of the lifecycle of the EntityManagers.  So, there does not seem
to be a need to do the findBroker(..) invocation, nor is there a need to keep track of the
created EntityManagers (_brokers) so that they can be closed when the Factory is closed.
> Once we have verified these changes, there may be others that are needed.  But, we have
to get by this bottleneck first before going to the next layer...
> Kevin

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message