[ http://issues.apache.org/jira/browse/JAMES-700?page=all ]
Robert Burrell Donkin updated JAMES-700:
----------------------------------------
Attachment: james-imap-runtime-catch.patch
This is the effective patch I'm running on my local James fork. This
corresponds to the no-reset version. This has made a big difference to my local
stability: before, James IMAP was effectively unusable for my data set.
However, I agree that it isn't the way forward. It does seem like the right
place for whatever solution is adopted.
Configurability is probably good. Perhaps introduce a configurable exception
handling strategy implementation executed here. This design would make it
easier for you to manage patches from my local fork.
> James resets connection when command throws RuntimeException
> ------------------------------------------------------------
>
> Key: JAMES-700
> URL: http://issues.apache.org/jira/browse/JAMES-700
> Project: James
> Issue Type: Improvement
> Components: IMAPServer
> Reporter: Robert Burrell Donkin
> Fix For: Trunk
>
> Attachments: james-imap-client-unstable.patch,
> james-imap-runtime-catch.patch
>
>
> I think that whenever a exception is thrown when processing an IMAP command
> the socket connection is reset. This behaviour seems little less polite than
> it needs to be. IMAP is stateless and IMHO errors should be returned within
> the band.
--
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]
