You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2020/02/07 03:11:00 UTC

[jira] [Created] (JAMES-3042) NullPointerException: Error while processing imap request

Benoit Tellier created JAMES-3042:
-------------------------------------

             Summary: NullPointerException: Error while processing imap request
                 Key: JAMES-3042
                 URL: https://issues.apache.org/jira/browse/JAMES-3042
             Project: James Server
          Issue Type: Improvement
          Components: IMAPServer
    Affects Versions: 3.4.0
            Reporter: Benoit Tellier


We encountered the following exception within one of our production environment:


{code:java}
 	java.lang.NullPointerException: null
	at org.apache.james.imapserver.netty.ImapRequestFrameDecoder.newCumulationBuffer(ImapRequestFrameDecoder.java:226)
	at org.jboss.netty.handler.codec.frame.FrameDecoder.updateCumulation(FrameDecoder.java:345)
	at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:312)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
	at org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.doRun(ChannelUpstreamEventRunnable.java:43)
	at org.jboss.netty.handler.execution.ChannelEventRunnable.run(ChannelEventRunnable.java:67)
	at org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$ChildExecutor.run(OrderedMemoryAwareThreadPoolExecutor.java:314)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

{code}


Apparently the issue is caused by a "NEEDED_DATA netty channel attachment not having been well positioned.

Super class method can be called in this case to be more resilient.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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