[ http://issues.apache.org/jira/browse/JAMES-678?page=comments#action_12448680 ] Bernd Fondermann commented on JAMES-678: ----------------------------------------
Currently, the message dumped to console counts 240 lines of redundant and uninformative stacktrace. This can be controlled from within AbstractJamesServer.initialize() only by not throwing the exception - which is a bad idea. Immediatly before re-throwing the exception, I propose to write a prominent and useful message to console + log: ... James Mail Server 3.0-dev ------------------------------- FATAL ERROR when starting service 'Remote Manager Service'! could not bind to 0.0.0.0:4555. Port is already in use by another application ------------------------------- (...avalanche of stack trace follows...) > Give helpful message when creating server sockets fails > ------------------------------------------------------- > > Key: JAMES-678 > URL: http://issues.apache.org/jira/browse/JAMES-678 > Project: James > Issue Type: Improvement > Reporter: Bernd Fondermann > Assigned To: Bernd Fondermann > > It is a common problem when starting James that server sockets (POP3, SMTP, > IMAP) are already bound by other applications or James is not given enough > rights to bind privileged ports. While this can't be fixed within James, > error messages given by James are confusing many users. > We should provide more extensive, verbose and helpful error messages. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]