----- Original Message ----- From: "Berin Loritsch" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> 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 assist, > 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. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4117 Server stops responding and processor usage goes up to 100% when I request with the XSP Generator a page that is not an XSP. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4298 If a <?xml-logicsheet href="/weborder/tagLibsWeborder.xsl"?> tag is put in an 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 requested. Nothing is specified in the log. Cocoon doesn't catch the error. See if current case fits into these. Ciao, Ken --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
