Thanks Hardy, Where can I start looking for changing the inner mechanics for how the pagenotfound error should be handled? Shouldn't it be handled more gracefully?
Is there even a good reason to have a full stack trace / dump for pagenotfound errors? Can anyone else confirm pagenotfound errors look the same way in your cocoon log (hundreds of lines long without explicitly stating what page was even requested)? Do you also have a happily functioning system with dozens / hour of this kind of error in your cocoon log as well? -- 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.
