ResponseIOException logged as error in DefaultExceptionMapper

[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-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org

[Sven Meier]

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)

Post by 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
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-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org

[Daniel Stoch]

WICKET-6565

--
Daniel

Post by Sven Meier
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)

Post by 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
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-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org