[
https://issues.apache.org/jira/browse/IMAP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Saladin updated IMAP-369:
---------------------------------
Description:
{code:title=Bar.java|borderStyle=solid}
Affects version (I could not choose this version in the Affects version
dropdown):
./lib/james-server-protocols-imap4-3.0-beta4.jar
When I connect to the James server using Thunderbird 11.0.1 as client with a
wrong username, and set the logging level of the James server to TRACE, I get
the following:
{code}
INFO 09:49:53,815 | james.imapserver | ID=553374 Connection established from
127.0.0.1
DEBUG 09:49:53,816 | james.imapserver | ID=553374 Got <tag>: 1
DEBUG 09:49:53,816 | james.imapserver | ID=553374 Got <command>: capability
DEBUG 09:49:53,817 | james.imapserver | ID=553374 No mailbox selected
DEBUG 09:49:56,901 | james.imapserver | ID=553374 Got <tag>: 2
DEBUG 09:49:56,901 | james.imapserver | ID=553374 Got <command>: authenticate
DEBUG 09:49:56,931 | james.imapserver | ID=553374 Got <tag>: 4
DEBUG 09:49:56,932 | james.imapserver | ID=553374 Got <command>: login
DEBUG 09:49:59,847 | james.imapserver | ID=553374 Got <tag>: 6
DEBUG 09:49:59,847 | james.imapserver | ID=553374 Got <command>: authenticate
INFO 09:49:59,849 | james.imapserver | ID=553374 Too many authentication
failures. Closing connection.
DEBUG 09:49:59,853 | james.imapserver | ID=553374 Error while processing imap
request
java.lang.NullPointerException
at
org.apache.james.imapserver.netty.ImapRequestFrameDecoder.createCumulationDynamicBuffer(ImapRequestFrameDecoder.java:211)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.cumulation(FrameDecoder.java:367)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:210)
at
org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.run(ChannelUpstreamEventRunnable.java:44)
at
org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$ChildExecutor.run(OrderedMemoryAwareThreadPoolExecutor.java:312)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
INFO 09:49:59,855 | james.imapserver | ID=553374 Connection closed for
127.0.0.1
INFO 09:49:59,887 | james.imapserver | ID=12914246 Connection established from
127.0.0.1
DEBUG 09:49:59,888 | james.imapserver | ID=12914246 Got <tag>: 1
DEBUG 09:49:59,888 | james.imapserver | ID=12914246 Got <command>: capability
DEBUG 09:49:59,889 | james.imapserver | ID=12914246 No mailbox selected
DEBUG 09:49:59,889 | james.imapserver | ID=12914246 Got <tag>: 2
DEBUG 09:49:59,890 | james.imapserver | ID=12914246 Got <command>: authenticate
DEBUG 09:49:59,892 | james.imapserver | ID=12914246 Got <tag>: 4
DEBUG 09:49:59,892 | james.imapserver | ID=12914246 Got <command>: login
INFO 09:50:03,090 | james.imapserver | ID=12914246 Connection closed for
127.0.0.1
INFO 09:53:26,765 | james.imapserver | Dispose IMAP Service
INFO 09:53:26,769 | james.imapserver | Dispose IMAP Service done
{code}
This happens with a very easy default configuration:
Correct username: bob@localhost
Wrong username: bob
It happens when connecting to the IMAP server using the wrong username (bob).
See attached TAR for whole configuration.
was:
{code:title=Bar.java|borderStyle=solid}
Affects version:
./lib/james-server-protocols-imap4-3.0-beta4.jar
When I connect to the James server using Thunderbird 11.0.1 as client with a
wrong username, and set the logging level of the James server to TRACE, I get
the following:
<code>
INFO 09:49:53,815 | james.imapserver | ID=553374 Connection established from
127.0.0.1
DEBUG 09:49:53,816 | james.imapserver | ID=553374 Got <tag>: 1
DEBUG 09:49:53,816 | james.imapserver | ID=553374 Got <command>: capability
DEBUG 09:49:53,817 | james.imapserver | ID=553374 No mailbox selected
DEBUG 09:49:56,901 | james.imapserver | ID=553374 Got <tag>: 2
DEBUG 09:49:56,901 | james.imapserver | ID=553374 Got <command>: authenticate
DEBUG 09:49:56,931 | james.imapserver | ID=553374 Got <tag>: 4
DEBUG 09:49:56,932 | james.imapserver | ID=553374 Got <command>: login
DEBUG 09:49:59,847 | james.imapserver | ID=553374 Got <tag>: 6
DEBUG 09:49:59,847 | james.imapserver | ID=553374 Got <command>: authenticate
INFO 09:49:59,849 | james.imapserver | ID=553374 Too many authentication
failures. Closing connection.
DEBUG 09:49:59,853 | james.imapserver | ID=553374 Error while processing imap
request
java.lang.NullPointerException
at
org.apache.james.imapserver.netty.ImapRequestFrameDecoder.createCumulationDynamicBuffer(ImapRequestFrameDecoder.java:211)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.cumulation(FrameDecoder.java:367)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:210)
at
org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.run(ChannelUpstreamEventRunnable.java:44)
at
org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$ChildExecutor.run(OrderedMemoryAwareThreadPoolExecutor.java:312)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
INFO 09:49:59,855 | james.imapserver | ID=553374 Connection closed for
127.0.0.1
INFO 09:49:59,887 | james.imapserver | ID=12914246 Connection established from
127.0.0.1
DEBUG 09:49:59,888 | james.imapserver | ID=12914246 Got <tag>: 1
DEBUG 09:49:59,888 | james.imapserver | ID=12914246 Got <command>: capability
DEBUG 09:49:59,889 | james.imapserver | ID=12914246 No mailbox selected
DEBUG 09:49:59,889 | james.imapserver | ID=12914246 Got <tag>: 2
DEBUG 09:49:59,890 | james.imapserver | ID=12914246 Got <command>: authenticate
DEBUG 09:49:59,892 | james.imapserver | ID=12914246 Got <tag>: 4
DEBUG 09:49:59,892 | james.imapserver | ID=12914246 Got <command>: login
INFO 09:50:03,090 | james.imapserver | ID=12914246 Connection closed for
127.0.0.1
INFO 09:53:26,765 | james.imapserver | Dispose IMAP Service
INFO 09:53:26,769 | james.imapserver | Dispose IMAP Service done
</code>
> NPE when connecting to apache-james-3.0-beta4 using incorrect user
> ------------------------------------------------------------------
>
> Key: IMAP-369
> URL: https://issues.apache.org/jira/browse/IMAP-369
> Project: JAMES Imap
> Issue Type: Bug
> Components: Protocol
> Reporter: Michael Saladin
> Attachments: adnjames_conf_folder.tar
>
>
> {code:title=Bar.java|borderStyle=solid}
> Affects version (I could not choose this version in the Affects version
> dropdown):
> ./lib/james-server-protocols-imap4-3.0-beta4.jar
> When I connect to the James server using Thunderbird 11.0.1 as client with a
> wrong username, and set the logging level of the James server to TRACE, I get
> the following:
> {code}
> INFO 09:49:53,815 | james.imapserver | ID=553374 Connection established from
> 127.0.0.1
> DEBUG 09:49:53,816 | james.imapserver | ID=553374 Got <tag>: 1
> DEBUG 09:49:53,816 | james.imapserver | ID=553374 Got <command>: capability
> DEBUG 09:49:53,817 | james.imapserver | ID=553374 No mailbox selected
> DEBUG 09:49:56,901 | james.imapserver | ID=553374 Got <tag>: 2
> DEBUG 09:49:56,901 | james.imapserver | ID=553374 Got <command>: authenticate
> DEBUG 09:49:56,931 | james.imapserver | ID=553374 Got <tag>: 4
> DEBUG 09:49:56,932 | james.imapserver | ID=553374 Got <command>: login
> DEBUG 09:49:59,847 | james.imapserver | ID=553374 Got <tag>: 6
> DEBUG 09:49:59,847 | james.imapserver | ID=553374 Got <command>: authenticate
> INFO 09:49:59,849 | james.imapserver | ID=553374 Too many authentication
> failures. Closing connection.
> DEBUG 09:49:59,853 | james.imapserver | ID=553374 Error while processing imap
> request
> java.lang.NullPointerException
> at
> org.apache.james.imapserver.netty.ImapRequestFrameDecoder.createCumulationDynamicBuffer(ImapRequestFrameDecoder.java:211)
> at
> org.jboss.netty.handler.codec.frame.FrameDecoder.cumulation(FrameDecoder.java:367)
> at
> org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:210)
> at
> org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.run(ChannelUpstreamEventRunnable.java:44)
> at
> org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$ChildExecutor.run(OrderedMemoryAwareThreadPoolExecutor.java:312)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> INFO 09:49:59,855 | james.imapserver | ID=553374 Connection closed for
> 127.0.0.1
> INFO 09:49:59,887 | james.imapserver | ID=12914246 Connection established
> from 127.0.0.1
> DEBUG 09:49:59,888 | james.imapserver | ID=12914246 Got <tag>: 1
> DEBUG 09:49:59,888 | james.imapserver | ID=12914246 Got <command>: capability
> DEBUG 09:49:59,889 | james.imapserver | ID=12914246 No mailbox selected
> DEBUG 09:49:59,889 | james.imapserver | ID=12914246 Got <tag>: 2
> DEBUG 09:49:59,890 | james.imapserver | ID=12914246 Got <command>:
> authenticate
> DEBUG 09:49:59,892 | james.imapserver | ID=12914246 Got <tag>: 4
> DEBUG 09:49:59,892 | james.imapserver | ID=12914246 Got <command>: login
> INFO 09:50:03,090 | james.imapserver | ID=12914246 Connection closed for
> 127.0.0.1
> INFO 09:53:26,765 | james.imapserver | Dispose IMAP Service
> INFO 09:53:26,769 | james.imapserver | Dispose IMAP Service done
> {code}
> This happens with a very easy default configuration:
> Correct username: bob@localhost
> Wrong username: bob
> It happens when connecting to the IMAP server using the wrong username (bob).
> See attached TAR for whole configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
