[ 
https://issues.apache.org/jira/browse/JAMES-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255440#comment-17255440
 ] 

ASF GitHub Bot commented on JAMES-3477:
---------------------------------------

jeantil commented on pull request #282:
URL: https://github.com/apache/james-project/pull/282#issuecomment-751610341


   >MimeMessageInputStreamSource (holding the reference to the deferedFile) is 
disposed, each references to opened stream get cleaned up, and the file is 
*deleted*. We should be good...
   Thats what I meant : I may be reading  MimeMessageInputStreamSource's code 
incorrectly but I don't see a reason that dispose cannot be called by a thread 
`t1` while another thread `t2` is trying to read the contents of one of the 
inputstream returned by `getInputStream()`
   `t2` is going to get `java.io.IOException: inputstream is closed` because 
`t1` disposed the message and we are back to data loss territory. 
   


----------------------------------------------------------------
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]

Reply via email to