[
https://issues.apache.org/jira/browse/JAMES-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255448#comment-17255448
]
ASF GitHub Bot commented on JAMES-3477:
---------------------------------------
jeantil commented on pull request #282:
URL: https://github.com/apache/james-project/pull/282#issuecomment-751616212
> Do you have exemples of situations when this can happen?
We discovered all this thread safety issue when debugging flaky tests: if
memory serves vacation mailet threw an error on a mail which triggered the
james error handling pipeline asynchronously. The initial pipeline ended up
completing while the error handling pipeline was scheduling the mail for
redelivery. This triggered a NPE because of the MMCOWP implementation at the
time, the currrent implementation may yield IOException instead of NPEs ...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> MimeMessageCopyOnWriteProxy is not thread safe
> ----------------------------------------------
>
> Key: JAMES-3477
> URL: https://issues.apache.org/jira/browse/JAMES-3477
> Project: James Server
> Issue Type: Wish
> Reporter: Benoit Tellier
> Priority: Major
>
> https://www.mail-archive.com/[email protected]/msg69221.html
> &
> https://github.com/jeantil/james-project/commit/c0354ea21c5b0a8f6d46e9919f7db0d97db9eb23
> proves there is a concurrency issue in MimeMessageCopyOnWriteProxy class that
> we need to investigate.
> It causes our test suite to be flacky.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
