Hi, regarding the OutOfMemory, they just added a max-instances attribute for entities and message driven beans in orion 1.4.6 - which by now is not accessible via autoupdate, it seems :-(. See bug #258. By now, the cache size depended only on the beans maximum lifetime (that is, a bean is removed only from the pool, if its timeout is reached, see the "validity-timeout" setting in orion-ejb-jar.xml). Best regards, Jens Stutte -----Ursprüngliche Nachricht----- Von: Satish Gupta [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 29. Januar 2001 21:39 An: Orion-Interest Betreff: Re: Does Orion provide Bean-pooling? Two comments! 1. I had to, occasionally, flush EJBCache to avoid getting a java.lang.OutOfMemory error, which, to me, implied that Orion was not passivating the beans! 2. Shouldn't there be a way to adjust the pool-size to tune the application? Too small a pool-size could 'choke' an application! Please comment. _______________ Pooling of Entity beans? Yes, it does. You can verify that for yourself by logging when orion calls the activate and passivate methods. No special setup is necessary. Nick ----- Original Message ----- From: Satish Gupta <mailto:[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Sent: Sunday, January 28, 2001 9:12 AM Subject: Does Orion provide Bean-pooling? It seems that the question "Does Orion provide Bean-pooling?" has been asked a few times on this mailing list but never answered explicitly. I'd appreciate somebody answering this question and, if available, how to set it up? None of the configuration files seem to have a provision for it. If it doesn't provide bean-pooling, are there any plans for it? Thanks Satish Gupta
