如果邮件服务器关闭，Apache Camel smtp 组件将挂起整个总线

发布于 2024-11-30 06:15:57 字数 1529 浏览 1 评论 0原文

我有一个我认为非常常见的场景。我有一个通过 Apache Camel 管理的发票系统。当出现问题时，我希望向管理员发送电子邮件警报。

在阅读了 Camel 异常处理之后，我想到了这个：（在我的 Spring XML 中）

<!-- General retrasmission policy set to 3 times -->
        <errorHandler id="deadChannel" type="DeadLetterChannel"
            deadLetterUri="direct:invoice-error">
            <redeliveryPolicy maximumRedeliveries="2"
                redeliveryDelay="1000" backOffMultiplier="2" useExponentialBackOff="true" />
        </errorHandler>

        <!-- Problematic invoices create email alerts to the administrator -->
        <route id="invoices-with-errors">
            <from uri="direct:invoice-error" />
            <bean ref="emailAlert" method="handleProblematicInvoice" />
            <to
                uri="smtp://{{errormail.host}}?to={{errormail.to}}&amp;subject={{errormail.subject}}&amp;from={{errormail.from}};debugMode=true;connectionTimeout=5000" />
        </route>

这对于我的用例来说OK。当抛出任何异常时，会发送电子邮件确实到了定义的地址。

但是，为了测试极端情况，我停止了内部电子邮件服务器以查看发生了什么发生。我预计 Camel 会尝试发送电子邮件，并在 5 秒后停止尝试（如上面 smpt URL 中的 connectionTimout 选项中所设置），

但实际上，整个 Camel 应用程序挂起！这简直让人无法接受！我不能保证邮件服务器会 100% 正常运行。

我在这里错过了什么吗？我是否应该完全放弃电子邮件警报的想法，或者 Camel 是否需要另一个特殊选项来在邮件服务器关闭时不挂起？

答案

该行

debugMode=true;connectionTimeout=5000

应该是

debugMode=true&amp;connectionTimeout=5000

原文

I have what I think is a very common scenario. I have an invoice system that is managed via Apache Camel. When something goes wrong I would like to have an email alert sent to the administrator.

After reading about Camel exception handling I came up with this: (inside my Spring XML)

<!-- General retrasmission policy set to 3 times -->
        <errorHandler id="deadChannel" type="DeadLetterChannel"
            deadLetterUri="direct:invoice-error">
            <redeliveryPolicy maximumRedeliveries="2"
                redeliveryDelay="1000" backOffMultiplier="2" useExponentialBackOff="true" />
        </errorHandler>

        <!-- Problematic invoices create email alerts to the administrator -->
        <route id="invoices-with-errors">
            <from uri="direct:invoice-error" />
            <bean ref="emailAlert" method="handleProblematicInvoice" />
            <to
                uri="smtp://{{errormail.host}}?to={{errormail.to}}&subject={{errormail.subject}}&from={{errormail.from}};debugMode=true;connectionTimeout=5000" />
        </route>

This works OK for my use case. When any exception is thrown an email is sent
indeed to the defined address.

However in order to test for corner cases I stopped the internal email server to see what
happens. I expected Camel to attempt an email send and stop trying after 5 seconds (as set in the connectionTimout option in the smpt URL above)

In reallity however the WHOLE Camel application hangs! This is simply unacceptable!
I cannot guarantee that the mail server will be up 100%.

Am I missing something here? Should I drop the idea of email alerts altogether or does Camel need another special option for NOT hanging when the mail server is down?

Answer

The line