Hello,

Thanks for the report.

This is a James bug.

The QResync (RFC-5162) is known to be buggy, and considered experimental.

I advise you to either:
 - Configure your client to no rely on QResync
 - Disable QResync capability advertising in James. This can be done in
imapserver.xml using the  <disabledCaps>QRESYNC</disabledCaps> tag.

See for instance https://issues.apache.org/jira/browse/JAMES-2278 which
seems to exactly be your issue.

Note that there is a fix available for that issue, but we miss a correct
testing strategy.

Cheers,

Benoit

Le 17/08/2018 à 01:56, Ashton Holmes a écrit :
> I neglected to include a stack trace in my original email:
> Aug 16 11:53:50 debian run.sh[29671]: WARN  11:53:50,942 |
> org.apache.james.imapserver.netty.ImapChannelUpstreamHandler | Error
> while processing imap request
> Aug 16 11:53:50 debian run.sh[29671]:
> java.lang.IndexOutOfBoundsException: Index: 6, Size: 6
> Aug 16 11:53:50 debian run.sh[29671]:         at
> java.util.ArrayList.rangeCheck(ArrayList.java:657)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> java.util.ArrayList.get(ArrayList.java:433)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imap.processor.AbstractSelectionProcessor.respond(Abst
> ractSelectionProcessor.java:234
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imap.processor.AbstractSelectionProcessor.doProcess(Ab
> stractSelectionProcessor.java:8
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imap.processor.AbstractSelectionProcessor.doProcess(Ab
> stractSelectionProcessor.java:6
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imap.processor.AbstractMailboxProcessor.doProcess(Abst
> ractMailboxProcessor.java:110)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imap.processor.AbstractMailboxProcessor.process(Abstra
> ctMailboxProcessor.java:97)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imap.processor.AbstractMailboxProcessor.doProcess(Abst
> ractMailboxProcessor.java:89)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imap.processor.AbstractMailboxProcessor.doProcess(Abst
> ractMailboxProcessor.java:71)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imap.processor.base.AbstractChainedProcessor.process(A
> bstractChainedProcessor.java:57
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imap.processor.base.AbstractChainedProcessor.process(A
> bstractChainedProcessor.java:66
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imap.processor.base.AbstractChainedProcessor.process(A
> bstractChainedProcessor.java:66
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.apache.james.imapserver.netty.ImapChannelUpstreamHandler.messageRec
> eived(ImapChannelUpstreamHandle
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(Sim
> pleChannelUpstreamHandler.java:
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChan
> nelPipeline.java:564)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerCon
> text.sendUpstream(DefaultChanne
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageRe
> ceived(FrameDecoder.java:462)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecode
> r.java:443)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameD
> ecoder.java:303)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(Sim
> pleChannelUpstreamHandler.java:
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChan
> nelPipeline.java:564)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerCon
> text.sendUpstream(DefaultChanne
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.doRun(Ch
> annelUpstreamEventRunnable.java
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.handler.execution.ChannelEventRunnable.run(ChannelEvent
> Runnable.java:67)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$
> ChildExecutor.run(OrderedMemory
> Aug 16 11:53:50 debian run.sh[29671]:         at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.ja
> va:1149)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.j
> ava:624)
> Aug 16 11:53:50 debian run.sh[29671]:         at
> java.lang.Thread.run(Thread.java:748)
> 
> On Thu, 2018-08-16 at 11:50 -0700, Ashton Holmes wrote:
>> I'm trying to use Evolution with james and sometimes Evolution will
>> give me the following message:
>> Failed to refresh folder “[email protected] : INBOX”. The reported
>> error was “Failed to select mailbox: Source stream returned no data”.
>>
>> Looking in my james log I have the following: 
>> WARN  22:56:33,976 | james.imapserver | ID=-1662004982 Error while
>> processing imap request: java.lang.IndexOutOfBoundsException - Index:
>> 6, Size: 6
>>
>> This issue occurs on both 3.0.1 and 3.1 and I'm not sure if a james
>> bug
>> or an evolution bug.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to