[jboss-jira] [JBoss JIRA] (WFCORE-3319) There should be replaced stacktrace loggings to stderr with usage of logging.
[
https://issues.jboss.org/browse/WFCORE-3319?page=com.atlassian.jira.plugi...
]
Romain Pelisse updated WFCORE-3319:
-----------------------------------
Description:
On many places both in server and in components there is called on exception
printStackTrace, this results in having the stacktrace printed to stderr. This results in
each line of the stacktrace to be considered a new error message in logs.
Using stderr is
1) is inefficient from performance point of view and
2) it doesn't have such nice control of what and when should be printed (length of
stacktrace,log level) as logging does.
I believe occurrences of using the printStackTrace in the code should be reviewed and
either removed or replaced with logging where appropriate.
There should be replaced stacktrace loggings to stderr with usage of
logging.
-----------------------------------------------------------------------------
Key: WFCORE-3319
URL: https://issues.jboss.org/browse/WFCORE-3319
Project: WildFly Core
Issue Type: Enhancement
Components: Server
Reporter: Romain Pelisse
Assignee: Priyanka Nag
Priority: Critical
On many places both in server and in components there is called on exception
printStackTrace, this results in having the stacktrace printed to stderr. This results in
each line of the stacktrace to be considered a new error message in logs.
Using stderr is
1) is inefficient from performance point of view and
2) it doesn't have such nice control of what and when should be printed (length of
stacktrace,log level) as logging does.
I believe occurrences of using the printStackTrace in the code should be reviewed and
either removed or replaced with logging where appropriate.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)