cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <ba...@webslingerZ.com>
Subject Re: couple of problems exposed under heavy load
Date Wed, 04 Jul 2001 03:16:37 GMT
On Mon, 2 Jul 2001, Berin Loritsch wrote:

> > heya. i recently got my tomcat-catalina and my apache talking to each
> > other, hurrah. i took the opportunity to load test my cocoon webapp.
> > overall, it held up pretty nicely, but when i cranked up the concurrency,
> > i started getting some exceptions here and there. one was:
> >
> > DEBUG   28325   [cocoon  ] (Ajp13Processor[8009][10]): UnnamedSelector:
> > ComponentSelector could not access the Component for hint: html
> > java.lang.Exception: Could not create enough Components to service your
> > request.
>
> This was probably due to limits of your JVM.  When we are getting Components
> from a pool, Excalibur (used by Cocoon) will create new instances of the
> Components when needed.  If the JVM cannot create a new Component, then it
> will throw an exception, and you will see the error message above.

how can i determine the underlying exception? if it's OutOfMemory, i'd
like to know that. i didn't see any OutOfMemoryExceptions in the log files
anywhere - or anything else which indicated a jvm problem creating a new
object.

- donald


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message