[
https://issues.apache.org/jira/browse/JAMES-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409875#comment-17409875
]
Benoit Tellier commented on JAMES-3589:
---------------------------------------
https://issues.apache.org/jira/browse/JAMES-1554 Funny stuff, bug report about
just this in 2014... :-/
> Matched mail resume processing from root
> ----------------------------------------
>
> Key: JAMES-3589
> URL: https://issues.apache.org/jira/browse/JAMES-3589
> Project: James Server
> Issue Type: Bug
> Components: MailStore & MailRepository
> Affects Versions: 3.5.0, 3.6.0
> Reporter: Benoit Tellier
> Priority: Major
> Fix For: 3.7.0, 3.6.1
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> h3. What
> One of my customer reported me that a side effect was done two time upon
> MailetContainer execution.
> What was not my surprise when writing integration tests counting executions,
> that they were right!
> Tracking down the bug, I encountered that `MailImpl.duplicate` do not
> preserve state, hence processing resumes from ROOT processor (leaving the
> exchange).
> h3. The fix
> MatcherSplitter should preserve the state of the matched mail.
> h3. The complications
> Preserving several mails on the same exchange, we should not shut the
> exchange down before processing is finished. Doing so would result in
> following I did set up reference counting for this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
