Hi, the problem of the maximum number of instances has been fixed some time ago. You have to provide an orion-ejb-jar.xml along with the ejb-jar.xml to give the server the information, how much instances for each EJB type may be used (without this, there seems to be no limit, only timeouts). It should look like this. <?xml version="1.0"?> <!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://www.orionserver.com/dtds/orion-ejb-jar.dtd";> <orion-ejb-jar> <enterprise-beans> <entity-deployment name="[Name]" location="[JNDI name]" max-instances="[Maximum number of instances]" validity-timeout="[timeout]" /> ... </enterprise-beans> </orion-ejb-jar> After you added this to your application, you should delete the application-deployment files and restart the server. While deploying the application, it should say something like "Copied deployment descriptor to ...". You can check it looking on the orion-ejb-jar.xml generated by the server among the deployed files: if your settings are in there (amongst others, automatically generated), everything works. Unfortunately there is no overall setting for all entity bean instances or, even better, a simple memory limit, which lets orion begin to free some (old) instances. You'll have to experiment with the number of instances and your application to see how it scales. My tip: choose a very high timeout and play around with the max-instances settings until you are satisfied with memory consumption. Regards, Jens Stutte > -----Ursprüngliche Nachricht----- > Von: Michael Jara [mailto:[EMAIL PROTECTED]] > Gesendet am: Mittwoch, 30. Mai 2001 20:40 > An: Orion-Interest > Betreff: Re: Orion running out of memory ? > > We have had similar problems, using Orion 1.4.5. > > The first problem seems to be that Orion does not re-use > instances... I > beleive that the orion-ejb-jar.xml defaults to allow an > infinite number of > instances per EJB. If you are creating a lot of instances, > this might help > your problem. > > The second problem seems to relate to bug#251. If you are performing > operations on entity beans, you might try setting their > "reentrant" property > to "true" and see if the problem goes away. If that works, I > think it is a > short-term workaround at best... I'm not sure how Orion > handles entity bean > reentrancy. > > Has anyone found these problems to be fixed in later (beta) > versions of > Orion? > > Mike > > ----- Original Message ----- > From: "Tony Fonager" <[EMAIL PROTECTED]> > To: "Orion-Interest" <[EMAIL PROTECTED]> > Sent: Wednesday, May 30, 2001 5:50 AM > Subject: Orion running out of memory ? > > > > I have a test website project, running on Orionserver - > after running for > > maybe 15-20 hours, it suddently stops working, with the > message : "Out of > > Memory - No Stack Trace Available" > > > > Is there some setting, where I setup the amount of memory for the > > Orionserver ? > > > > I have monitored "memory usage" and it keeps growing during the test > period, > > until it suddently stops working, with the above memory error. > > > > What can I do - either there is a leak or it uses > incredible much memory. > > > > (I dont use any objects, which earlier has been mentioned > on this list for > > leaking!) > > > > Any ideas, people ? > > > > > > - > > Regards, > > Tony Fonager > > > > Netcoders ApS - http://www.netcoders.dk > > > >
