[
https://issues.apache.org/jira/browse/JAMES-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254955#comment-17254955
]
ASF GitHub Bot commented on JAMES-3477:
---------------------------------------
jeantil commented on pull request #281:
URL: https://github.com/apache/james-project/pull/281#issuecomment-751323163
I have seen #282 and I'll definitely vote for it :)
Can you confirm the following about the logs above
- you were using the patch from #280 in a live system
- you still observed the concurrency issue with the patch applied
And expand on this from #282
> Attempts to make it thread safe like [2] [...] ultimately did not manage
to protect 'optimized' raw access to the underlying data thus not fully
addressing the concurrency issues.
Do you know what the 'optimized' raw access you speak of is and where and
when it used to occur ? I'm curious because dispose would set the ref to
underlying to null but
----------------------------------------------------------------
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]
