Bug 56086 - Exceptions not thrown, simply printed to stack trace
Summary: Exceptions not thrown, simply printed to stack trace
Status: NEW
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Appender (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-29 11:56 UTC by olaf
Modified: 2014-01-29 11:56 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description olaf 2014-01-29 11:56:05 UTC 
As i wanted to start a TelnetAppender with a Port that is already in use, to handle the Error and inform the User that he should choose an other Port, you simply:

catch(IOException e) {
   e.printStackTrace();
}

*(TelnetAppender line 76-87)*

And i cannot use the Error anymore. I don't know if this was intended but it sure is useless in this form. (Not only the TelnetAppender)