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 "Benoit Tellier (Jira)" <se...@james.apache.org> on 2020/05/29 05:16:00 UTC

[jira] [Created] (JAMES-3197) MailetProcessor should handle NoClassDefFoundError

Benoit Tellier created JAMES-3197:
-------------------------------------

             Summary: MailetProcessor should handle NoClassDefFoundError
                 Key: JAMES-3197
                 URL: https://issues.apache.org/jira/browse/JAMES-3197
             Project: James Server
          Issue Type: Improvement
          Components: Mailet Contributions
            Reporter: Benoit Tellier


Due to JAMES-3176, we ended up having ExtractMDNOriginalJMAPMessageId throwing NoClassDefFoundError.

This error is not handled by the mailet processor, resulting in a mailqueue nack, and generated an infinite loop on top of RabbitMQ.

This error can happen too when a user specifies a custom mailet with unsatisfied dependencies.

Thus, when a mailet, or a matcher throws a `NoClassDefFoundError` we should execute mailet error handling normally, and prevent that infinite loop.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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