mirror of https://github.com/apache/openjpa.git
OPENJPA-160. Docs updates.
git-svn-id: https://svn.apache.org/repos/asf/incubator/openjpa/trunk@513189 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
dc797ab923
commit
af1796f17c
|
@ -574,7 +574,8 @@ collection of results can speed up data loading by orders of magnitude.
|
|||
</para>
|
||||
</entry>
|
||||
<entry colname="desc">
|
||||
By default, OpenJPA's EntityManagers use finalizers to ensure that resources
|
||||
Outside of a Java EE 5 application server or other JPA persistence container,
|
||||
OpenJPA's EntityManagers use finalizers to ensure that resources
|
||||
get cleaned up. If you are properly managing your resources, this finalization
|
||||
is not necessary, and will introduce unneeded synchronization, leading to
|
||||
scalability problems. You can disable this protective behavior by setting the
|
||||
|
|
|
@ -119,14 +119,16 @@ and <classname>Broker</classname>s.
|
|||
</secondary>
|
||||
</indexterm>
|
||||
<para>
|
||||
The default OpenJPAEntityManager implementation automatically closes itself
|
||||
during instance finalization. This guards against accidental resource leaks
|
||||
that may occur if a developer fails to explicitly close EntityManagers when
|
||||
finished with them, but it also incurs a scalability bottleneck, since the
|
||||
JVM must perform synchronization during instance creation, and since the
|
||||
finalizer thread will have more instances to monitor. To avoid this overhead,
|
||||
set the <link linkend="openjpa.BrokerImpl"><literal>openjpa.BrokerImpl</literal>
|
||||
</link> configuration property to <literal>non-finalizing</literal>.
|
||||
Outside of a Java EE 5 application server or other JPA persistence container
|
||||
environment, the default OpenJPAEntityManager implementation automatically
|
||||
closes itself during instance finalization. This guards against accidental
|
||||
resource leaks that may occur if a developer fails to explicitly close
|
||||
EntityManagers when finished with them, but it also incurs a scalability
|
||||
bottleneck, since the JVM must perform synchronization during instance creation,
|
||||
and since the finalizer thread will have more instances to monitor. To avoid
|
||||
this overhead, set the
|
||||
<link linkend="openjpa.BrokerImpl"><literal>openjpa.BrokerImpl</literal></link>
|
||||
configuration property to <literal>non-finalizing</literal>.
|
||||
</para>
|
||||
</section>
|
||||
<section id="ref_guide_runtime_broker_extension">
|
||||
|
|
Loading…
Reference in New Issue