Hello I have the same problem, orion just keeps making new beans, in the mentioned test case, orion will simply allocate all available memory until the application goes java.lang.OutOfMemory exception or just goes dog-slow. The problem is not just related to entity beans, but session beans as well, stateless AND statefull, the problem is just much more visible with entity beans, cause they're usually instantiated alot more than session beans.
I solved the entity bean issue by issuing a " max instances = 10 " or similar inthe deployment descriptor, however i don't have this option with session beans !! So allthought he problem persist, the server can run for a longer amount of time before memory allocation becomes an issue. Orion version : is actually Oracles OC4J 9.0.2.0.0, i dont know how to translate that into a specific orion version at the moment (suggestions ?) -----Oprindelig meddelelse----- Fra: Lachezar Dobrev [mailto:[EMAIL PROTECTED]] Sendt: 8. marts 2002 12:15 Til: Orion-Interest Emne: Container does not passivate my beans. Hello. I sent a message some days ago, to no avail. It didn't show up in the list. My problem is, that Orion does not passivate my beans. I have tested both CMP and BMP, with NO success... I ran a test, which created 1 million bean instances. Orion kept up creating beans, until at last it ran out of memory (740MB). Am i doing something wrong? for (int i = 0; i < 1000000; i ++){ MyHome.create(i); } No success... 1 million. If these are not released imagine what will happen at a later moment? I need to create beans continuously. Do I have to restart Orion every couple of minutes, just to clear the bean pools? I must say I'm very disappointed. I don't see reason to use Entity Beans any more. I better serialize to files. THAT will do the job. Later all. Lachezar
