Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@jakarta.apache.org Received: (qmail 20726 invoked by uid 500); 8 Jun 2001 13:14:00 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: "Avalon Development" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 20381 invoked from network); 8 Jun 2001 13:13:52 -0000 Message-ID: <3B20CF34.618475F8@apache.org> Date: Fri, 08 Jun 2001 09:12:20 -0400 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Avalon Development Subject: Re: AW: [4.0b1]: Exception when creating new components References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Carsten Ziegeler wrote: > > > Berin Loritsch wrote: > > > > Carsten Ziegeler wrote: > > > > > > Hi, > > > > > > I am using the beta 1 of Cocoon 2 which uses Avalon 4.0b1. > > > On my linux machine (sun jdk 1.3.1) I get from time to > > > time under some load the following exception: > > > > > > "Could not create enough Components to service your request" > > > > > > This exception is thrown in the DefaultPool implementation. > > > > > > What could be the reason for this? > > > > > > Could it either be a threading problem or could it be that > > > we didn't release all components? > > > > Is this with the JdbcDataSourceComponent? If so, it uses > > the HardResourceLimitingPool which extends the DefaultPool > > implementation. > > > No, it is the DefaultComponentManager trying to get another XSLT > transformer. > The error occurs only sometimes and simply reloading the page > solves the problem. > > > Another possibility is that the JDK can't respond quick enough > > because under load, new components are created. > > > > Can you please give some more information--it will help track > > down what is happening? > > If it helps, we could try to regenerate the error on Monday > and send the whole cocoon.log. Ok. Keep in mind that if the TraxTransformer fails at any point during initialization (constructor through init lifecycle phase), the Pool will return the exception you are seeing. Check the TraxTransformer for potential weak areas. It is a complex beast. --------------------------------------------------------------------- To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: avalon-dev-help@jakarta.apache.org