[ http://issues.apache.org/jira/browse/DIRMINA-143?page=comments#action_12359910 ]
Walter Tam commented on DIRMINA-143: ------------------------------------ Wrapping would be the logical choice. However in this case the IOException being thrown does not support wrapping. A possible solution is to throw a subclass of IOException with a constructor that takes a Throwable arguemnt. > SocketAcceptor.bind() should fillInStackTrace() before rethrowing exception > --------------------------------------------------------------------------- > > Key: DIRMINA-143 > URL: http://issues.apache.org/jira/browse/DIRMINA-143 > Project: Directory MINA > Type: Bug > Versions: 0.8.1 > Reporter: Walter Tam > Priority: Minor > > When SocketAcceptor.bind() encounters an exception returned from the bind > request, it simply rethrows. The resulting stack trace is from the underlying > registration thread which is not very helpful when debugging the cause. Other > similar places like SocketAcceptor.unbind(), DatagramAcceptor.unbind() does a > fillInStackTrace() before re throwing. > Also it will be helpful in this case to add the port number that failed to > the message -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
