camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5376) Mail component disconnect in the wrong way
Date Tue, 19 Jun 2012 05:16:42 GMT


Claus Ibsen commented on CAMEL-5376:

Can you post more details, such as the route you use? And the stacktrace as well.
> Mail component disconnect in the wrong way
> ------------------------------------------
>                 Key: CAMEL-5376
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-mail
>    Affects Versions: 2.9.1
>         Environment: Outlook 2010, but should happen with any mail server, since it is
not directly related to (See above)
>            Reporter: Alexis Kinsella
> The way disconnect is implemented causes issues with some other options of the consumer.
For instance "disconnect" option is not compatible with "delete" option.
> The delete action is done in completion action (processCommit: line 185). On line 305,
processCommit method checks if folder is open, but "disconnect" option force folder at null
value at the end of poll method (Line 149).
> I guess disconnect method should be called on completion after any other completion actions
occured: It is not possible to make completion actions if connection to mail server is closed.
> The result of the usage of disconnect option and delete option is a NullPointerException
on test: "if (!folder.isOpen())" statement on line 308.
> Issue should be always reproductible.
> I let you fix the priority of the issue, but it is an annoying issue even if there is
a workaround by disabling disconnect option ...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message