You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Berin Loritsch <bl...@apache.org> on 2001/12/26 20:58:55 UTC
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?
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: IMPORTANT: Current CVS hangs
Posted by Nicola Ken Barozzi <ba...@nicolaken.com>.
----- Original Message -----
From: "Berin Loritsch" <bl...@apache.org>
To: <co...@xml.apache.org>
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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: IMPORTANT: Current CVS hangs
Posted by Berin Loritsch <bl...@apache.org>.
Bernhard Huber wrote:
> hi,
> just a quick idea: the StoreJanitor perhaps?
It is possible, however I have used the tuning guide, and I have no luck
in finding a suitable setting. This has never been the case before.
Please, if you have any clue that will help, let me know.
> I experience that current CVS when build the documentation you have to
> leave main with
> exit(), otherwise it hangs.
> bye benrhard
>
> Berin Loritsch wrote:
>
>> 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?
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
> .
>
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: IMPORTANT: Current CVS hangs
Posted by Bernhard Huber <be...@a1.net>.
hi,
just a quick idea: the StoreJanitor perhaps?
I experience that current CVS when build the documentation you have to
leave main with
exit(), otherwise it hangs.
bye benrhard
Berin Loritsch wrote:
> 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?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org