]
Radoslav Husar updated MODCLUSTER-413:
--------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Merged.
Log superfluous stack traces onto DEBUG instead of ERROR level
--------------------------------------------------------------
Key: MODCLUSTER-413
URL:
https://issues.jboss.org/browse/MODCLUSTER-413
Project: mod_cluster
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Core & Container Integration (Java)
Affects Versions: 1.3.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Fix For: 1.3.1.Final
(18:17:45) rhusar: pferraro: i would like to refactor this: when modcluster fails certain
calls on the proxy, the whole stack trace is logged
(18:17:59) rhusar: pferraro: and i think its really useless to log Connection failed
stack trace
(18:18:07) rhusar: pferraro: some projects solve this by
(18:18:08) rhusar: pferraro:
ContextLogger.LOG.unableToClearBeanStore(getBeanStore());
(18:18:08) rhusar: ContextLogger.LOG.catchingDebug(e);
(18:18:18) rhusar: pferraro: would you be in favor of such change?
(18:19:27) rhusar: pferraro: so you can still access the stack traces if you switch to
debug. otherwise things like restarting the proxy doesnt print a horrific stack trace
(18:19:31) rhusar: pferraro: just an error.
(18:20:15) pferraro: rhusar: that makes sense
(18:20:40) rhusar: pferraro: ie get rid of
https://gist.githubusercontent.com/rhusar/6ddc5b3b0ce51d4f6f67/raw/137d12...