You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Joachim Draeger <jd...@gmx.de> on 2006/11/20 19:34:01 UTC

Re: [jira] Commented: (JAMES-700) James resets connection when command throws RuntimeException

Am Montag, den 20.11.2006, 12:48 +0100 schrieb Stefano Bagnara:

> > I hope we'll be able to wipe out the most annoying RuntimeExceptions soon. 
> > IMO catching RuntimeException would lead to undefined behavior and would make reporting bugs more diffuse. 
> > At the moment I don't see a problems with merging, if there are only a few lines to catch exceptions.

> Maybe after having applied JAMES-710 something changed in this regard 
> because the default behaviour of AbstractJamesHandler is to catch 
> RuntimeException.

Isn't the RuntimeException just caught in:

AbstractJamesHandler.handleConnection(Socket connection) 

try {
 handleProtocol(); 
} catch (RuntimeException e) {
...
}

The "command-loop" is in handleProtocol(), so the connection would be
reset anyway when there is a RE in a command. Right? :)

Joachim



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org