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

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

Github user nstdio commented on a diff in the pull request:

    https://github.com/apache/james-project/pull/127#discussion_r202304791
  
    --- Diff: 
server/queue/queue-jms/src/test/java/org/apache/james/queue/jms/JMSMailQueueTest.java
 ---
    @@ -49,7 +49,8 @@ public void setUp(BrokerService broker) throws Exception {
             RawMailQueueItemDecoratorFactory mailQueueItemDecoratorFactory = 
new RawMailQueueItemDecoratorFactory();
             NoopMetricFactory metricFactory = new NoopMetricFactory();
             String queueName = BrokerExtension.generateRandomQueueName(broker);
    -        mailQueue = new JMSMailQueue(connectionFactory, 
mailQueueItemDecoratorFactory, queueName, metricFactory);
    +        ConsumerOptions consumerOptions = name -> name + 
"?consumer.prefetchSize=0";
    --- End diff --
    
    Yes, in fact its a good idea, solving multiple problems/inconsistencies 
with a single shot.
    
    Please, clarify how do you see the `JMSConsumerOptions` object creation? It 
would be through `new` or through builder class?
    
    What do you think about both options combined together (public constructor 
+ builder) ?
    
    In case of builder, I suppose we should expose single `put(String, String)` 
and provide users context free consumer options builder.


> 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: Tellier Benoit
>            Priority: Major
>              Labels: bug
>
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

Reply via email to