Hi! What has to be done in order to limit the maximal number of instantiated or pooled entity bean instances in the EJB container? We tried following settings in orion-ejb.jar: <entity-deployment name="Tpersonen" location="Tpersonen" wrapper="TpersonenHome_EntityHomeWrapper33" max-tx-retries="3" max-instances="30" table="Tpersonen" data-source="jdbc/FQSDDataSource" exclusive-write-access="false" instance-cache-timeout="30" pool-cache-timeout="30"> fields, finder methods, etc. </ entity-deployment> Then we use a test client to execute findAll() method on TpersonenHome. As this method invocation touches all bean instances in a single transaction, all instances are loaded (approximately 500 instances). So far so good. But after the transaction is committed (Number of transactions in progress is 0), we still have all instances loaded by the container, and this instances stay loaded until the server shutdown, even after several hours of inactivity. We are able to reset the number of instances in cache only by pressing the "flush cache" button in the console. Another strange thing is that only approximately a third of the memory that was used when all instances are instantiated or pooled is released after the "flush cache" button is pressed. So even if one presses the "flush cache" button from time to time, we will run out of the memory sooner or later. Any help would be greatly appreciated, Cheers Ivo P.S.: We are using Orion 1.5.2. on W2K.
