JMS与Spring Integration，消除对 ActiveMQ 实例的依赖

Question

我最近将一些日志记录设置为 AcitveMQ 作为即发即忘服务，以便应用程序可以仅向“ActivityLoggingChannel”发送消息，而不必处理日志记录的横切问题。

所有内容都发送到 ActivityLoggingGateway，它只是一个具有默认通道的接口。然后查询 Pojo（动态路由器）的通道名称以获取消息端点。动态路由器有一个 JMX 入口点，它允许我动态切换端点。如果消息端点设置为jmsChannelSender，并且无法解析ActiveMQ url，则会导致整个系统崩溃。

我遇到的问题是，如果无法访问 ActiveMQ URL，我希望系统恢复到使用简单的多线程进程中方法的不同消息通道。

下面是 spring 集成配置。使用版本 2.0.0.RELEASE

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xmlns:context="http://www.springframework.org/schema/context"
    xmlns:int="http://www.springframework.org/schema/integration"
    xmlns:jms="http://www.springframework.org/schema/integration/jms"
    xmlns:int-jmx="http://www.springframework.org/schema/integration/jmx"
    xsi:schemaLocation="http://www.springframework.org/schema/jms http://www.springframework.org/schema/jms/spring-jms-3.0.xsd
        http://www.springframework.org/schema/integration http://www.springframework.org/schema/integration/spring-integration-2.0.xsd
        http://www.springframework.org/schema/integration/jmx http://www.springframework.org/schema/integration/jmx/spring-integration-jmx-2.0.xsd
        http://www.springframework.org/schema/integration/jms http://www.springframework.org/schema/integration/jms/spring-integration-jms-2.0.xsd
        http://www.springframework.org/schema/integration/stream http://www.springframework.org/schema/integration/stream/spring-integration-stream-2.0.xsd
        http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
        http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd
        http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd">

    <import resource="dm-activitylogging-services.xml"/>

    <bean name="decisionActivityLoggingAspect" class="com.idna.dm.aspects.logging.activity.DecisionActivityLogAspect" 
        factory-method="aspectOf">
        <property name="activityLoggingGateway">
            <ref bean="activityLoggingGateway" />
        </property>
    </bean>

<!-- New Activity Logging Services Reference dm-activity-logging -->    
<!-- JMS Channel Adapter -->
    <int:channel id="jmsSenderChannel" />

    <bean id="destinationLocalQueue" class="org.apache.activemq.command.ActiveMQQueue">
        <constructor-arg index="0" value="${activemq.queuename.activitylogging}" />
    </bean>

    <bean id="connectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
        <property name="brokerURL" value="${activemq.url}" />
    </bean>

    <bean id="activityLogConverter" class="com.idna.dm.domain.activitylogging.jms.ActivityLogConverter" />
    <jms:outbound-channel-adapter channel="jmsSenderChannel"  destination="destinationLocalQueue" connection-factory="connectionFactory" message-converter="activityLogConverter"/>

<!--  In Process Adapter -->

    <int:channel id="inProcessChannel" />   
    <int:outbound-channel-adapter channel="inProcessChannel" ref="inProcessAdapter" method="persistLog" />
    <bean id="inProcessAdapter" class="com.idna.dm.logging.activity.impl.InProcessActivityLoggingImpl" >
        <property name="activityLoggingService" >
            <ref bean="activityLogging" />
        </property>
    </bean>

    <int:channel id="asyncInProcessChannel" />
    <int:outbound-channel-adapter channel="asyncInProcessChannel" ref="asyncInProcessAdapter" method="persistLog" />
    <bean id="asyncInProcessAdapter" class="com.idna.dm.logging.activity.impl.AsyncInProcessActivityLoggingImpl" >
        <property name="activityLoggingService">
            <ref bean="activityLogging" />
        </property>
    </bean>

<!-- Custom channel for console output using the router -->

    <!-- Console Channel 
    <int:channel id="consoleAdapterChannel" />
    <int:outbound-channel-adapter channel="consoleAdapterChannel" ref="consoleAdapter" method="printToStdout" />
    <bean id="consoleAdapter" class="com.idna.dm.logging.activity.util.StdoutTargetAdapter" />
     -->

    <!-- Log4j Channel -->
    <int:channel id="loggingChannel" />
    <int:logging-channel-adapter auto-startup="true" level="INFO" log-full-message="true" channel="loggingChannel" />

<!-- Router -->
    <int:gateway id="activityLoggingGateway" 
        service-interface="com.idna.dm.logging.activity.logger.ActivityLoggingGateway" />


    <int:channel id="activityLoggingChannel" />

    <int:router input-channel="activityLoggingChannel" ref="dynamicRouter"
        method="route" default-output-channel="asyncInProcessChannel"
        ignore-channel-name-resolution-failures="true" />

    <bean id="dynamicRouter" class="com.idna.dm.logging.activity.router.DynamicRouter">
        <constructor-arg index="0" value="asyncInProcessChannel" />
    </bean>

Answer 1

您可以使用故障转移机制来实现它：

<channel id="input">
  <dispatcher load-balancer="none"/>
</channel>

<service-activator input-channel="input" order="1"/>

<service-activator input-channel="input" order="2"/>

在这种情况下，第一个将始终首先被调用。
只有当第一个失败时才执行第二个。

默认情况下，故障转移为true。