[
https://issues.apache.org/jira/browse/JAMES-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482402#comment-17482402
]
Ilja Weis commented on JAMES-3709:
----------------------------------
Hello,
in the test that caused the exception there were no parallel POP3 sessions
connecting to the same account, but it should be the same session.
The way (I believe) I can reproduce the original problem (inconsistency between
the pop3metadata and imapuidtable tables) is by stopping James while it is
handling POP3 sessions where a number of messages are being deleted. Currently
trying to reproduce with the latest James, I can provide some details if it's
helpful.
But considering you can reproduce it your way, perhaps it's the same problem?
We're using distributed-pop3-app by the way.
> Missing null check in POP3 TopCmdHandler
> ----------------------------------------
>
> Key: JAMES-3709
> URL: https://issues.apache.org/jira/browse/JAMES-3709
> Project: James Server
> Issue Type: Bug
> Components: protocols
> Affects Versions: master
> Reporter: Karsten Otto
> Priority: Major
> Attachments: error.txt
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> TopCmdHandler is missing a null check when retrieving the message content,
> i.e. the InputStream can be null, which results in an NPE down the line.
> Admittedly this is a rare case, I only observed this during heavy load
> testing.
> On closer inspection it turns out that TopCmdHandler duplicates a major
> portion of code from RetrCmdHandler, but with subtle differences such as the
> null check mentioned above.
> I propose to refactor the two classes to make them share the code, and
> provide unit tests for all possible error/success cases.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
