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

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:
Patrick Linskey 2007-03-01 06:43:00 +00:00
parent dc797ab923
commit af1796f17c
2 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
openjpa-project/src/doc/manual/ref_guide_optimization.xml
View File

@ -574,7 +574,8 @@ collection of results can speed up data loading by orders of magnitude.
</para> </para>
</entry> </entry>
<entry colname="desc"> <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 get cleaned up. If you are properly managing your resources, this finalization
is not necessary, and will introduce unneeded synchronization, leading to is not necessary, and will introduce unneeded synchronization, leading to
scalability problems. You can disable this protective behavior by setting the scalability problems. You can disable this protective behavior by setting the

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

@ -119,14 +119,16 @@ and <classname>Broker</classname>s.
</secondary> </secondary>
</indexterm> </indexterm>
<para> <para>
The default OpenJPAEntityManager implementation automatically closes itself Outside of a Java EE 5 application server or other JPA persistence container
during instance finalization. This guards against accidental resource leaks environment, the default OpenJPAEntityManager implementation automatically
that may occur if a developer fails to explicitly close EntityManagers when closes itself during instance finalization. This guards against accidental
finished with them, but it also incurs a scalability bottleneck, since the resource leaks that may occur if a developer fails to explicitly close
JVM must perform synchronization during instance creation, and since the EntityManagers when finished with them, but it also incurs a scalability
finalizer thread will have more instances to monitor. To avoid this overhead, bottleneck, since the JVM must perform synchronization during instance creation,
set the <link linkend="openjpa.BrokerImpl"><literal>openjpa.BrokerImpl</literal> and since the finalizer thread will have more instances to monitor. To avoid
</link> configuration property to <literal>non-finalizing</literal>. this overhead, set the
<link linkend="openjpa.BrokerImpl"><literal>openjpa.BrokerImpl</literal></link>
configuration property to <literal>non-finalizing</literal>.
</para> </para>
</section> </section>
<section id="ref_guide_runtime_broker_extension"> <section id="ref_guide_runtime_broker_extension">