Is it possible that this incredibly verbose error output (as many as 1500 lines) is all due to a simple *page not found* error?
Could someone test this in their 5_x repository and confirm that a fake handle (or any url that doesn't exist in the system) generates this super-long error in your cocoon log? Note the time to make it easier to track it. Also, if I am interpreting my error logs correctly, it looks like sometimes the 'page not found' gets triggered on a request for the favicon which is weird since it always seems present to me in the browser tab. Here's our newly launched site to see for yourself: https://cardinalscholar.bsu.edu/ In the page-structure.xsl I have the following to present that icon. <link rel="shortcut icon"> <xsl:attribute name="href"> <xsl:value-of select="/dri:document/dri:meta/dri:pageMeta/dri:metadata[@element='contextPath'][not(@qualifier)]"/> <xsl:text>/themes/</xsl:text> <xsl:value-of select="/dri:document/dri:meta/dri:pageMeta/dri:metadata[@element='theme'][@qualifier='path']"/> <xsl:text>/images/favicon.ico</xsl:text> </xsl:attribute> </link> and then (somehow) right before one of the "Failed to process pipeline" notices I see the following: 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache HIT for PK_G-file-file:///E:/dspace/webapps/xmlui/aspects/protodocument.xml 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/9 /favicon.ico?pipelinehash=477348137205522819_T-Navigation-6131973275261880188 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/8 /favicon.ico?pipelinehash=-5023394907477727460_T-Navigation-3212562138654597485 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/7 /favicon.ico?pipelinehash=-1941327661434669097_T-Navigation-3212562138654597485 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/6 /favicon.ico?pipelinehash=26815437322659760_T-SystemwideAlerts-1_T-Navigation--5367372201529954577 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/5 /favicon.ico?pipelinehash=-4170905213321689863_T-Navigation-5799876941772906259 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/4 /favicon.ico?pipelinehash=7562864311120640244 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/3 /favicon.ico?pipelinehash=-1058144055897292008 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/2 /favicon.ico?pipelinehash=-738220103570222181 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/1 /favicon.ico?pipelinehash=147586322582675017_T-PageNotFound--242969834922413342 2016-02-16 00:35:50,783 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-file-cocoon://DRI/favicon.ico?pipelinehash=-4234072418721460733_T-IncludePageMeta--5280603869656992694_T-IncludePageMeta-7145676799531262490_T-IncludePageMeta-1889180249406810576_T-xslt-file:///E:/dspace/webapps/xmlui/themes/BSU/BSU.xsl_T-i18n-context://i18n/?en_US__S-xhtml-;doctype-public=-//W3C//DTD XHTML 1.0 Strict//EN;doctype-system=http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;encoding=UTF-8;indent=yes 2016-02-16 00:35:50,783 ERROR cocoon.handled - *Failed to process pipeline* ... The descending order of DRI/#/favicon.ico right before the pipeline error looks *so odd* to me. What is happening there? Is it trying to find the favicon set up via page-structure.xsl? I suspect it is something else since every page load doesn't generate these logs. I don't know if it is related, but my dspace.cfg file has the following line which *does not exist*: websvc.opensearch.faviconurl = http://www.dspace.org/images/favicon.ico I don't think we are intentionally trying to make "opensearch" work. Could that be causing this error? Also, I hope that page not found errors eventually get re-written to be more useful; in particular, printing the URL that 'could not be found' as part of the error message would be great. Not every failed to process pipeline output message deserves 1500 lines, IMHO -- particularly for most page not found errors I can imagine. -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
