On 16.07.2004 04:44, Nandakumar Mounasamy wrote:
We are getting "internal server error" from cocoon 212 under high load, or moderate load over 30-60 minutes of run. The issue is very consistent and has very similar error patterns in the cocoon logs. We run Cocoon 2 on JBoss 3.2.3 and JRE 142_05. On every occurrence of this error, the message below is first logged in sitemap log.
WARN (2004-07-15) 20:39.56:734 [sitemap] (/cocoon/index.xml) TP-Processor10/ExcaliburComponentSelector: Attempted to release a org.apache.cocoon.transformation.TraxTransformer but its handler could not be located.
...
WARN (2004-07-15) 20:54.56:730 [sitemap] (/cocoon/index.xml) TP-Processor30/ExcaliburComponentManager: ComponentLocator exception from parent CM during lookup.
org.apache.avalon.framework.component.ComponentException: Could not find component (key [org.apache.cocoon.components.pipeline.ProcessingPipelineSelector])
at org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburCompon
entManager.java:295) ....
Soon after the message below is repeated on all other cocoon logs, until the severs are restarted.
ERROR (2004-07-15) 20:54.56:988 [access] (/cocoon/index.xml) TP-Processor30/CocoonServlet: Internal Cocoon Problem
org.apache.avalon.framework.component.ComponentException: UnnamedSelector: ComponentSelector Attempted to retrieve component with null hint.
at org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(ExcaliburCompo
nentSelector.java:223)
...
We have also noticed that the error occurs (reported in cocoon logs) randomly with other components also, like a) ERROR (2004-07-15) 08:22.44:872 [sitemap] (/cocoon/index.xml)
TP-Processor26/ErrorHandlerHelper: An exception occured in while handling errors
at file:/jboss/ONE/server/default/deploy/c2.war/sitemap.xmap:1660:24
org.apache.cocoon.ProcessingException: Lookup of generator for role 'notifying' f
ailed.: org.apache.avalon.framework.component.ComponentException: generators: Com
ponentSelector could not find the component for hint [notifying] (key [notifying]
)
at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setGe
nerator(AbstractProcessingPipeline.java:254)
b) ERROR (2004-07-14) 22:33.37:193 [sitemap.handled-errors] (/cocoon/index.xml) TP-Processor14/PipelineNode: Lookup of serializer for role 'html' failed.
org.apache.cocoon.ProcessingException: Lookup of serializer for role 'html' faile
d.: org.apache.avalon.framework.component.ComponentException: serializers: Compon
entSelector could not find the component for hint [html] (key [html])
at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setSe
rializer(AbstractProcessingPipeline.java:320)
I have attached the various cocoon logs. Is this a known bug with cocoon 212 or Avalon? Is there a fix or work around existing for this issue?
Such issues are mostly hard to reproduce, so it's hard to say whether exactly the cause for the above behaviour was fixed or not. IIRC there have been fixed some issues on component retrieval, but if it was before or after 2.1.2 I don't know. So I can only recommend to try the more recent 2.1.5.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
