[
https://issues.apache.org/jira/browse/JAMES-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2295.
---------------------------------
Resolution: Fixed
>From what I can see the initial issue won't happen anymore because the dequeue
>semantic changed (ie reactor migration).
Having prefetch for ActiveMQ might make sense on a performance standpoint but I
think that it is not required for correctness.
As such I will close this PR and ticket.
Thanks again for your time on diagnostic and proposing a fix.
Best regards,
Benoit
> JMS mailqueue deadlock when a single thread issue several consume
> -----------------------------------------------------------------
>
> Key: JAMES-2295
> URL: https://issues.apache.org/jira/browse/JAMES-2295
> Project: James Server
> Issue Type: Bug
> Components: Queue
> Affects Versions: 3.0.0, master, 3.0.1
> Reporter: Benoit Tellier
> Priority: Major
> Labels: bug
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This will lead to a dead lock:
> {code:java}
> MailQueue.MailQueueItem mailQueueItem1 = getMailQueue().deQueue();
> MailQueue.MailQueueItem mailQueueItem2 = getMailQueue().deQueue();
> mailQueueItem1.done(true);
> mailQueueItem2.done(true);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
