cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ken Barozzi" <>
Subject Re: IMPORTANT: Current CVS hangs
Date Wed, 26 Dec 2001 22:42:09 GMT

----- Original Message -----
From: "Berin Loritsch" <>
To: <>
Sent: Wednesday, December 26, 2001 8:58 PM
Subject: IMPORTANT: Current CVS hangs

> The Cocoon currently hands when using XSP:
> DEBUG   (2001-12-26) 14:52.14:632   [cocoon  ] (/index.html)
Thread-6/GeneratorSelector: Could not access component for hint:
> org\apache\cocoon\www\docs\login_xsp
> DEBUG   (2001-12-26) 14:52.14:632   [cocoon  ] (/index.html)
Thread-6/ProgramGeneratorImpl: The instance was not accessible from the
> internal cache. Proceeding.
> DEBUG   (2001-12-26) 14:52.14:642   [cocoon  ] (/index.html)
Thread-6/ProgramGeneratorImpl: The class was not preloaded
> The last message remains the last message, CPU processing is pegged,
> and no errors are reported.
> This appears to either be a deadlock or an infinite loop.  Can anyone
> or give clues?

It's not the first time that Cocoon deadlocks this way.
I submitted two bug reports on this, but unfortunately didn't have time to
investigate further.
Server stops responding and processor usage goes up to 100% when I request
the XSP Generator a page that is not an XSP.
If a <?xml-logicsheet href="/weborder/tagLibsWeborder.xsl"?> tag is put in
Xsp and the file is not present, the server responds with a generic error
stacktrace that says basically that Cocoon wasn't able to process the Url
Nothing is specified in the log.
Cocoon doesn't catch the error.

See if current case fits into these.


To unsubscribe, e-mail:
For additional commands, email:

View raw message