You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Steffen Eitelmann (JIRA)" <ji...@apache.org> on 2016/08/19 08:24:20 UTC
[jira] [Updated] (CAMEL-10254) Error may still block mail-consumer
[ https://issues.apache.org/jira/browse/CAMEL-10254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steffen Eitelmann updated CAMEL-10254:
--------------------------------------
Description:
If an error occurs before routing an email (email corrupt), the consumer blocks and does not process further emails. A similar issue was fixed with CAMEL-7474, but the issue still exists at another location.
CAMEL-7474 introduced a parameter "skipFailedMessage", which is used in Line 291 of the MailConsumer. If an error occurs in "createExchanges" (Line 128) the parameter is not evaluated.
Example stacktrace:
{code}
2016.08.19 10:10:35.613 DEBUG Camel (camel-1) thread #52 - pop3s://dev1@dev.de) Error populating the initial mail message attachments
org.apache.camel.RuntimeCamelException: Error populating the initial mail message attachments
at org.apache.camel.component.mail.MailMessage.populateInitialAttachments(MailMessage.java:131)
at org.apache.camel.impl.DefaultMessage.createAttachments(DefaultMessage.java:216)
at org.apache.camel.impl.DefaultMessage.getAttachments(DefaultMessage.java:281)
at org.apache.camel.component.mail.MailConsumer.createExchanges(MailConsumer.java:328)
at org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:121)
at org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.mail.MessagingException: Missing start boundary
at javax.mail.internet.MimeMultipart.parsebm(MimeMultipart.java:882)
at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:503)
at javax.mail.internet.MimeMultipart.getCount(MimeMultipart.java:244)
at org.apache.camel.component.mail.MailBinding.extractAttachmentsFromMultipart(MailBinding.java:304)
at org.apache.camel.component.mail.MailBinding.extractAttachmentsFromMail(MailBinding.java:293)
at org.apache.camel.component.mail.MailMessage.populateInitialAttachments(MailMessage.java:128)
... 13 more
{code}
Results are the same as described in CAMEL-7474
was:
If an error occurs before routing an email (email corrupt), the consumer blocks and does not process further emails. A similar issue was fixed with CAMEL-7474, but the issue still exists on another location.
CAMEL-7474 introduced a parameter "skipFailedMessage", which is used in Line 291 of the MailConsumer. If an error occurs in "createExchanges" (Line 128) the parameter is not evaluated.
Example stacktrace:
{code}
2016.08.19 10:10:35.613 DEBUG Camel (camel-1) thread #52 - pop3s://dev1@dev.de) Error populating the initial mail message attachments
org.apache.camel.RuntimeCamelException: Error populating the initial mail message attachments
at org.apache.camel.component.mail.MailMessage.populateInitialAttachments(MailMessage.java:131)
at org.apache.camel.impl.DefaultMessage.createAttachments(DefaultMessage.java:216)
at org.apache.camel.impl.DefaultMessage.getAttachments(DefaultMessage.java:281)
at org.apache.camel.component.mail.MailConsumer.createExchanges(MailConsumer.java:328)
at org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:121)
at org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.mail.MessagingException: Missing start boundary
at javax.mail.internet.MimeMultipart.parsebm(MimeMultipart.java:882)
at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:503)
at javax.mail.internet.MimeMultipart.getCount(MimeMultipart.java:244)
at org.apache.camel.component.mail.MailBinding.extractAttachmentsFromMultipart(MailBinding.java:304)
at org.apache.camel.component.mail.MailBinding.extractAttachmentsFromMail(MailBinding.java:293)
at org.apache.camel.component.mail.MailMessage.populateInitialAttachments(MailMessage.java:128)
... 13 more
{code}
Results are the same as described in CAMEL-7474
> Error may still block mail-consumer
> ------------------------------------
>
> Key: CAMEL-10254
> URL: https://issues.apache.org/jira/browse/CAMEL-10254
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
> Affects Versions: 2.15.3, 2.17.3
> Reporter: Steffen Eitelmann
>
> If an error occurs before routing an email (email corrupt), the consumer blocks and does not process further emails. A similar issue was fixed with CAMEL-7474, but the issue still exists at another location.
> CAMEL-7474 introduced a parameter "skipFailedMessage", which is used in Line 291 of the MailConsumer. If an error occurs in "createExchanges" (Line 128) the parameter is not evaluated.
> Example stacktrace:
> {code}
> 2016.08.19 10:10:35.613 DEBUG Camel (camel-1) thread #52 - pop3s://dev1@dev.de) Error populating the initial mail message attachments
> org.apache.camel.RuntimeCamelException: Error populating the initial mail message attachments
> at org.apache.camel.component.mail.MailMessage.populateInitialAttachments(MailMessage.java:131)
> at org.apache.camel.impl.DefaultMessage.createAttachments(DefaultMessage.java:216)
> at org.apache.camel.impl.DefaultMessage.getAttachments(DefaultMessage.java:281)
> at org.apache.camel.component.mail.MailConsumer.createExchanges(MailConsumer.java:328)
> at org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:121)
> at org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
> at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.mail.MessagingException: Missing start boundary
> at javax.mail.internet.MimeMultipart.parsebm(MimeMultipart.java:882)
> at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:503)
> at javax.mail.internet.MimeMultipart.getCount(MimeMultipart.java:244)
> at org.apache.camel.component.mail.MailBinding.extractAttachmentsFromMultipart(MailBinding.java:304)
> at org.apache.camel.component.mail.MailBinding.extractAttachmentsFromMail(MailBinding.java:293)
> at org.apache.camel.component.mail.MailMessage.populateInitialAttachments(MailMessage.java:128)
> ... 13 more
> {code}
> Results are the same as described in CAMEL-7474
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)