Serge Knystautas wrote:
>
> Federico Barbieri wrote:
> > Theoretically the best way to manage exception should be: if some error
> > occur that the mail servlet can somhow administer it's up to the servlet
> > to act the best (send back mail to sender, reties later, ignore or fix
> > the problem etc. ). If the exception is somehow unpredictable the
> > reactor will move unprocessed mail to a UnableToProcess Repository
> > logging the exception and notify the administrator.
>
> I would agree that the servlet API should not support throwing any
> exceptions. But runtime exceptions (such as
> ArrayIndexOutOfBoundsException) can't be designed away.
Something like:
try {
servlet.service(MessageContainer mc);
} catch (Throwable t) {
...
}
> I like the idea
> of the UnableToProcess repository... although it'd be good to know which
> servlet sent the message there so once we fix things, the admin can
> return those messages to the pipeline.
Need more time to think about it... I was wondering if restarting from
the originl message could be better. The failing mail could be just used
as message in log to better identify the problem.
>
> Serge
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/>
> Problems?: [EMAIL PROTECTED]
--
Federico
*-----------------------------------*
"Troubles occurr when two people try
to be intelligent in the same time."
- Murphy
*-----------------------------------*
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
