Lachezar, I know it'd be a hack, but I have seen some on the archieve a workaround that flushed the cache manually directly calling to Orion API. I do not prefer this, but might help you temporarily.
Search on the mail archieve for the workaround or put your problem on the Atlassian Forum. It has proved to me really responsive, and actually, I think many of us are interested in the solution. Cheers, Tibor -----Original Message----- From: Lachezar Dobrev [mailto:[EMAIL PROTECTED]] Sent: Saturday, March 09, 2002 3:09 PM To: Orion-Interest Subject: Re: Container does not passivate my beans. Hello. Well... I'm using "Orion/1.5.2 (build 10460)" for reasons other than the beans. Well actually I do need more that 10 million rows. No, they are not created withing one and the same transaction. Each one is created in a different transaction (the code I posted was an excerpt of a stand-alone client using com.evermind.server.rmi.RMIInitialContextFactory. The database itself has no problems with a 1 million rows, but the container does not passivate/clear/rele4ase the beans with time. They keep growing and growing. The test beans had only an Integer primary key and no data fields at all. The "real-life" beans will hold 1-2K data. You can see the problem... 10K beans will be around 20MB data only. Too much for me. I tried some tune-up settings, but could not get any results except with the 'exclusive-write-access="false"', but in that case I get only one bean generated, and that shits the hell out of me. I just need to set some sensible time-out value, but neither instance-cache-timeout, nor validity-timeout, nor pool-cache-timeout, nor max-instances did the job for me. Non of these changed the logics. If the exclusive-write-access is true, a bean instance gets generated every time I create an entity. If set to false I get enormous lag for using the beans. That is not good. Isn't there any setting, that can tell orion to flush the bean instances every let's say 10 seconds? Thanks for the help anyway. A food for thought. Looking forward for some helper settings. Lachezar. > Hi, > What version are you using? > I saw this problem in 1.0.2.2, but not 1.0.2.2.1 the same way. > > Do you really need to create 1,000,000 rows in one transaction, or will > it actually be many transactions? If I create 1000 beans/transaction, > and call it many times, it seems I only ever have 1000 total used/pooled > instances. > > I did change instance-cache-timeout="1" for the entity bean I am testing. > > Another change I made (for different reasons) was to set > exclusive_write_acesss= "false", I don't know if that effected this at all. > > hope this helps, > Roxanne > > Lachezar Dobrev wrote: > > > 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 > > > > > > > > -- > > =============================== > Roxanne Tapia > Bioscience Division (B-1) > Los Alamos National Laboratory > 505-665-0206 > =============================== > > >
