edit the orion-ejb-jar.xml file in
/$ORION_HOME$/application-deployments/$YOUR_PROJECT$-ejb.jar directory. set
the attribute max-instances='x' in all the EJBs deployed, where x is the
maximum number of EJBs you allow in memory at any time. this will prevent
your system from 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 secon
Java? Memory leak? Um, not likely.
Make sure you don't have some kind of infinite loop in your application. I
did that once, and got the error after Orion grew to 512MB of RAM, used up
all the swap space too, then orion tried to recover and it couldn't.
If you ask me, I think it does a good
Try (just for a test) to have some servlet/ejb,... run from time to time
a System.gc(); We have seen in our servlet-environments that free-memory
would shrink in continuation... calling gc() from time to time would free
the memory again. Cannot really explain the whereabouts, but it might work
f
