You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@james.apache.org by GitBox <gi...@apache.org> on 2020/12/26 06:12:41 UTC

[GitHub] [james-project] jeantil edited a comment on pull request #281: JAMES-3477 Disable copy on write through system property

jeantil edited a comment 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 if the 'optimized' access already had the reference it shouldn't have failed...


----------------------------------------------------------------
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:
users@infra.apache.org



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