You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Daniel Stoch <da...@gmail.com> on 2018/06/26 14:30:46 UTC
ResponseIOException logged as error in DefaultExceptionMapper
Hi,
DefaultExceptionMapper handles by default some "internal" exceptions.
You can look at the thread "Marker interface for "internal"
exceptions" on this list (Jun 02, 2014). ResponseIOException is one of
them, but when this kind of exception occurs then an error is logged
in DefaultExceptionMapper.mapExpectedExceptions(...):
logger.error("Connection lost, give up responding.", e);
Why it is logged as an error, which means something is wrong in our
application? If it is handled transparently by a framework then it
should not be logged as error (maybe as debug?).
Or maybe I should add some special handling to this
ResponseIOException in my app?
--
Best regards,
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: ResponseIOException logged as error in DefaultExceptionMapper
Posted by Daniel Stoch <da...@gmail.com>.
WICKET-6565
--
Daniel
On Tue, Jun 26, 2018 at 11:19 PM Sven Meier <sv...@meiers.net> wrote:
>
> Hi,
>
> I agree that a warning would be more appropriate, maybe we don't need
> the stacktrace either.
>
> Please create an issue.
>
> Thanks
> Sven
>
>
> (WICKET-3570)
>
>
> Am 26.06.2018 um 16:30 schrieb Daniel Stoch:
> > Hi,
> >
> > DefaultExceptionMapper handles by default some "internal" exceptions.
> > You can look at the thread "Marker interface for "internal"
> > exceptions" on this list (Jun 02, 2014). ResponseIOException is one of
> > them, but when this kind of exception occurs then an error is logged
> > in DefaultExceptionMapper.mapExpectedExceptions(...):
> >
> > logger.error("Connection lost, give up responding.", e);
> >
> > Why it is logged as an error, which means something is wrong in our
> > application? If it is handled transparently by a framework then it
> > should not be logged as error (maybe as debug?).
> > Or maybe I should add some special handling to this
> > ResponseIOException in my app?
> >
> > --
> > Best regards,
> > Daniel
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: ResponseIOException logged as error in DefaultExceptionMapper
Posted by Sven Meier <sv...@meiers.net>.
Hi,
I agree that a warning would be more appropriate, maybe we don't need
the stacktrace either.
Please create an issue.
Thanks
Sven
(WICKET-3570)
Am 26.06.2018 um 16:30 schrieb Daniel Stoch:
> Hi,
>
> DefaultExceptionMapper handles by default some "internal" exceptions.
> You can look at the thread "Marker interface for "internal"
> exceptions" on this list (Jun 02, 2014). ResponseIOException is one of
> them, but when this kind of exception occurs then an error is logged
> in DefaultExceptionMapper.mapExpectedExceptions(...):
>
> logger.error("Connection lost, give up responding.", e);
>
> Why it is logged as an error, which means something is wrong in our
> application? If it is handled transparently by a framework then it
> should not be logged as error (maybe as debug?).
> Or maybe I should add some special handling to this
> ResponseIOException in my app?
>
> --
> Best regards,
> Daniel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org