EJB Memory Use
Written by Joseph Ottinger
Orion has a tendency to hold cached entity beans for quite some time, which can lead to perceived memory leaks (and certainly expanded memory use.) One way to control this is to modify orion-ejb-jar.xml to include an attribute to specify max-instances. You will need to play with this attribute and the validity-timeout attribute for your application in order to get the best performance (along with the exclusive-write-access attribute). A truncated example:
<orion-ejb-jar>
<enterprise-beans>
<entity-deployment name="MyBean" location="MyBean"
max-instances="10"
validity-timeout="6000"
exclusive-write-access="true"
</enterprise-beans>
</orion-ejb-jar>
Copyright © 2007 IronFlare AB