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: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
