[JAMES-2672] Some Mail instance can have a null name

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 3.4.0
• Assignee: Unassigned
• Reporter: Matthieu Baechler
• Created: 26/Feb/19 15:34
• Updated: 06/Mar/19 10:26
• Resolved: 06/Mar/19 10:26

Description

During a stress test, I encountered this kind of errors :

java.lang.NullPointerException: null
        at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:877)
        at org.apache.james.queue.rabbitmq.view.api.DeleteCondition.withName(DeleteCondition.java:170)
        at org.apache.james.queue.rabbitmq.Dequeuer.lambda$ack$1(Dequeuer.java:106)
        at com.github.fge.lambdas.consumers.ThrowingConsumer.accept(ThrowingConsumer.java:22)
        at org.apache.james.queue.rabbitmq.Dequeuer$RabbitMQMailQueueItem.done(Dequeuer.java:62)
        at org.apache.james.jmap.send.PostDequeueDecorator.done(PostDequeueDecorator.java:80)
        at org.apache.james.mailetcontainer.impl.JamesMailSpooler.lambda$run$0(JamesMailSpooler.java:164)

It looks like there's some code path that allows a Mail to have a null name.

Issue Links

• is cloned by: JAMES-2679 Some Mail instance can have a null name