Hi Robert, Of course this is not an offical and documented way and I would it never use in production. It's the result of playing around with the orion-console and analyzing the interface "ApplicationAdministrator" with javap. Heinz -----Ursprüngliche Nachricht----- Von: Robert Krueger [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 8. November 2000 10:56 An: Orion-Interest Betreff: Re: AW: Entity beans never changed back to the pool. At 08:12 08.11.00 , you wrote: >Hello Esteban, > >I posted the same question some months ago. >In this list there are several mails concerning the cache-strategy of >entity-beans in the orion-container - but unfortunately we never got answers >from the developer-team. > >I found a way to flush the cache automatically. > >You can use the class > com.evermind.server.administration.ApplicationAdministrator >from orion.jar in the following way (application-client or session-bean): > >... >import com.evermind.server.administration.*; >... >Context context = new InitialContext(); >ApplicationAdministrator admin = >(ApplicationAdministrator)context.lookup("java:comp/Administrator"); >... >admin.flushEJBCache("name of your entity-bean"); >... is this offically exposed and documented? if not, what makes you think they don't change the interface in the next version regardless of whether you've coded against it? robert >All beans will be flushed, it works fine. >But the virtual memory of the JVM don't change (WinNT, JDK 1.3, Orion >1.4.0). > >Kind regards > >Heinz Häußler >Eurocopter Deutschland GmbH >D/KDC >Postfach 13 53 >86603 Donauwörth >Tel.: +49 (0) 906 / 71-4431 >Fax.: + 49 (0) 906 / 71-4100 >Mail: mailto:[EMAIL PROTECTED] >Home: http:\\www.eurocopter.com > >-----Ursprüngliche Nachricht----- >Von: Lopez Esteban [mailto:[EMAIL PROTECTED]] >Gesendet am: Montag, 6. November 2000 20:07 >An: Orion-Interest >Betreff: Entity beans never changed back to the pool. > >Hello, I plan to use Orion-Server for a big Database-Application with Java- >and Web-Clients. >I'm using Orion version 1.4.0. After serveral tests we noticed, that once a >Entity-Bean was instanced and used, it never changed back to the pool. The >number of usered instances grows and grows until I manually flush the cache >in the Console-Utility. >With this strategy, the Server will run out of memory after some time. Is it >possible to limit the number of used and pooled Entity-Bean instances ? I >can't find any parameter in the xml-Files. >Best regards >Esteban > (-) Robert Krüger (-) SIGNAL 7 Gesellschaft für Informationstechnologie mbH (-) Brüder-Knauß-Str. 79 - 64285 Darmstadt, (-) Tel: 06151 665401, Fax: 06151 665373 (-) [EMAIL PROTECTED], www.signal7.de
