ERROR - ResourceRequestTarget - Error writing resource data to content / how brix should handle this?

[Korbinian]

Hi,

finally we dployed our public brix app, and all went quite well so
far. However, in the logs I regularly see 2 types of entries that are
reported as ERROR, but IMHO shouldnt be:

ERROR - ResourceRequestTarget - Error writing resource data to
contentjava.lang.RuntimeException:
org.apache.catalina.connector.ClientAbortException:
java.io.IOException: Connection reset by peer at
org.brixcms.plugin.site.resource.Streamer.stream(Streamer.java:
110) ......

and

ERROR - ResourceRequestTarget - Error writing resource data to
contentjava.lang.RuntimeException:
org.apache.catalina.connector.ClientAbortException:
java.io.IOException: Broken pipe at
org.brixcms.plugin.site.resource.Streamer.stream(Streamer.java:110)
a.....

So, as those errors are both client based I don't know if its good to
have Brix report those. However, before just swallowing those I kindly
wanted to ask if there is any use of getting these things into the
server-logs.

Best,

Korbinian

[D S]

Hi Korbinian,

My log is also full of these errors and I agree that it isn't necessary.

Best,

Dan

--
You received this message because you are subscribed to the Google Groups "brix-cms-discuss" group.
To post to this group, send email to brix-cms...@googlegroups.com.
To unsubscribe from this group, send email to brix-cms-discu...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/brix-cms-discuss?hl=en.

[Korbinian]

Ok,

I'll suggest a fix in Streamer.java at lines 103-115:

if
(Application.get().getConfigurationType().equals(RuntimeConfigurationType.DEVELOPMENT))
{
if (e.getClass().getName().contains("Eof")) {
// ignore
} else {
throw new RuntimeException(e);
}
} else {
//in deployment mode we will not report any
ClientAbortExceptions;
if(!
e.getClass().getName().contains("ClientAbortException")) {
throw new RuntimeException(e);
}
}

I'll add it to github in next 1-3 days

On 7 Mai, 16:37, D S <wicke...@gmail.com> wrote:
> Hi Korbinian,
>
> My log is also full of these errors and I agree that it isn't necessary.
>
> Best,
>
> Dan
>