cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <vgritse...@hns.com>
Subject RE: couple of problems exposed under heavy load
Date Mon, 02 Jul 2001 13:39:56 GMT
Donald,

This might help you with pools:

http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99244034515731&w=2

However, does it work in sitemap (for html, xslt, etc components) or not - I don't know...

Vadim

> -----Original Message-----
> From: Donald Ball [mailto:balld@webslingerZ.com]
> Sent: Sunday, July 01, 2001 16:52
> To: cocoon-dev@xml.apache.org
> Subject: couple of problems exposed under heavy load
> 
> 
> 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.
>         at
> org.apache.avalon.excalibur.pool.DefaultPool.get(DefaultPool.java:135)
>         at
> org.apache.avalon.excalibur.component.PoolableComponentHandler.get(PoolableComponentHandler.java:117)
>         at
> org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(ExcaliburComponentSelector.java:246)
>         at
> org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:49)
> 
> another was:
> 
> WARN    27933   [cocoon  ] (Ajp13Processor[8009][4]): Pool interrupted
> while waiting for lock.
> java.lang.NullPointerException
>         at
> com.webslingerZ.cocoon2.transformation.InspectionTransformer.recycle(InspectionTransformer.java:82)
>         at
> org.apache.avalon.excalibur.pool.DefaultPool.put(DefaultPool.java:169)
>         at
> org.apache.avalon.excalibur.component.PoolableComponentHandler.put(PoolableComponentHandler.java:131)
>         at
> org.apache.avalon.excalibur.component.ExcaliburComponentSelector.release(ExcaliburComponentSelector.java:350)
> 
> (which is probably my bug, but i thought the 'Pool interrupted while
> waiting for lock' message was strange)
> 
> and another one of these:
> 
> DEBUG   27779   [cocoon  ] (Ajp13Processor[8009][4]): UnnamedSelector:
> ComponentSelector could not access the Component for hint: xslt
> java.lang.Exception: Could not create enough Components to service your
> request.
>         at
> org.apache.avalon.excalibur.pool.DefaultPool.get(DefaultPool.java:135)
>         at
> org.apache.avalon.excalibur.component.PoolableComponentHandler.get(PoolableComponentHandler.java:117)
>         at
> org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(ExcaliburComponentSelector.java:246)
>         at
> org.apache.cocoon.sitemap.SitemapComponentSelector.select(SitemapComponentSelector.java:49)
> 
> avalon guys, do you have any suggestions for settings i could tweak to try
> to make the component handlers scale up a bit more?
> 
> - donald
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 
> 

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


Mime
View raw message