[
https://issues.apache.org/jira/browse/JAMES-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3197.
---------------------------------
Fix Version/s: 3.6.0
3.5.0
Resolution: Fixed
> 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
> Priority: Major
> Labels: bug
> Fix For: 3.5.0, 3.6.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
