This occurs when a socket was reset and or incorrectly disconnected. I would imagine that it does not print to the log to prevent the log from being filled with these exceptions. The exception should be completely suppressed and the disconnect should be noted.
On Sun, Feb 3, 2019 at 7:14 AM Michael Kunze (JIRA) <[email protected]> wrote: > Michael Kunze created DIRMINA-1100: > -------------------------------------- > > Summary: printStackTrace in AbstractPollingIoProcessor:1109 > Key: DIRMINA-1100 > URL: https://issues.apache.org/jira/browse/DIRMINA-1100 > Project: MINA > Issue Type: Improvement > Components: Core > Affects Versions: 2.0.19 > Reporter: Michael Kunze > > > I'm using a SMTP server based on mina and i seem to run into this catch > block in AbstractPollingIoProcessor:1109 > {code:java} > try { > localWrittenBytes = write(session, buf, length); > } catch (IOException ioe) { > ioe.printStackTrace(); > > // We have had an issue while trying to send data to the > // peer : let's close the session. > buf.free(); > session.closeNow(); > this.removeNow(session); > > return 0; > } > {code} > Well on the internet there all kinds of crooked smtp clients around, so i > see the exception quite often. What i don't like that is printed on > standard error instead of using the embedded logging. > > Is it possible to change the line: > {code:java} > ioe.printStackTrace(); > {code} > into > {code:java} > LOG.error("Issue while trying to send data to the peer. Closing > connection.", ioe); > {code} > > > That way i can decide if i care about it and maybe silence that one. > > > > Thanks! > > > > -- > This message was sent by Atlassian JIRA > (v7.6.3#76005) >
