Spring JMS - 无法使用嵌入式代理连接到代理 URL

Posted 2023-03-10

【中文标题】Spring JMS - 无法使用嵌入式代理连接到代理 URL

【英文标题】：Spring JMS - Unable to connect to broker URL with embedded Broker

【发布时间】：2015-08-31 00:34:27

【问题描述】：

这是我的 JmsMessageSender

@Service
public class JmsMessageSender 

    @Autowired
    private JmsTemplate jmsTemplate;


    /**
     * send text to default destination
     * @param text
     */
    public void send(final String text) 

        this.jmsTemplate.send(new MessageCreator() 
            @Override
            public Message createMessage(Session session) throws JMSException 
                Message message = session.createTextMessage(text);
                return message;
            
        );
    

    /**
     * Simplify the send by using convertAndSend
     * @param text
     */
    public void sendText(final String text) 
        this.jmsTemplate.convertAndSend(text);
    

    /**
     * Send text message to a specified destination
     * @param text
     */
    public void send(final Destination dest,final String text) 

        this.jmsTemplate.send(dest,new MessageCreator() 
            @Override
            public Message createMessage(Session session) throws JMSException 
                Message message = session.createTextMessage(text);
                return message;
            
        );
    

这是我的演示类

public class DemoMain 

    public static void main(String[] args) 
        // init spring context
        ApplicationContext ctx = new ClassPathXmlApplicationContext("context.xml");

        // get bean from context
        JmsMessageSender jmsMessageSender = (JmsMessageSender)ctx.getBean("jmsMessageSender");

        // send to default destination
        jmsMessageSender.send("hello JMS");

        // send to a code specified destination
        Queue queue = new ActiveMQQueue("AnotherDest");
        jmsMessageSender.send(queue, "hello Another Message");

        // close spring application context
        ((ClassPathXmlApplicationContext)ctx).close();
    

我的 context.xml

还有我的 activemq.xml 配置。

<beans
        xmlns="http://www.springframework.org/schema/beans"
        xmlns:amq="http://activemq.apache.org/schema/core"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
  http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">

    <!-- Allows us to use system properties as variables in this configuration file -->
    <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
        <property name="locations">
            <value>file:$activemq.conf/credentials.properties</value>
        </property>
    </bean>

    <!--
        The <broker> element is used to configure the ActiveMQ broker.
    -->
    <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="activemq-data">

        <!--
            For better performances use VM cursor and small memory limit.
            For more information, see:

            http://activemq.apache.org/message-cursors.html

            Also, if your producer is "hanging", it's probably due to producer flow control.
            For more information, see:
            http://activemq.apache.org/producer-flow-control.html
        -->

        <destinationPolicy>
            <policyMap>
                <policyEntries>
                    <policyEntry topic=">" producerFlowControl="true">
                        <!-- The constantPendingMessageLimitStrategy is used to prevent
                             slow topic consumers to block producers and affect other consumers
                             by limiting the number of messages that are retained
                             For more information, see:

                             http://activemq.apache.org/slow-consumer-handling.html

                        -->
                        <pendingMessageLimitStrategy>
                            <constantPendingMessageLimitStrategy limit="1000"/>
                        </pendingMessageLimitStrategy>
                    </policyEntry>
                    <policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb">
                        <!-- Use VM cursor for better latency
                             For more information, see:

                             http://activemq.apache.org/message-cursors.html

                        <pendingQueuePolicy>
                          <vmQueueCursor/>
                        </pendingQueuePolicy>
                        -->
                    </policyEntry>
                </policyEntries>
            </policyMap>
        </destinationPolicy>


        <!--
            The managementContext is used to configure how ActiveMQ is exposed in
            JMX. By default, ActiveMQ uses the MBean server that is started by
            the JVM. For more information, see:

            http://activemq.apache.org/jmx.html
        -->
        <managementContext>
            <managementContext createConnector="false"/>
        </managementContext>

        <!--
            Configure message persistence for the broker. The default persistence
            mechanism is the KahaDB store (identified by the kahaDB tag).
            For more information, see:

            http://activemq.apache.org/persistence.html
        -->
        <persistenceAdapter>
            <kahaDB directory="activemq-data/kahadb"/>
        </persistenceAdapter>


        <!--
          The systemUsage controls the maximum amount of space the broker will
          use before slowing down producers. For more information, see:
          http://activemq.apache.org/producer-flow-control.html
          If using ActiveMQ embedded - the following limits could safely be used:

      <systemUsage>
          <systemUsage>
              <memoryUsage>
                  <memoryUsage limit="20 mb"/>
              </memoryUsage>
              <storeUsage>
                  <storeUsage limit="1 gb"/>
              </storeUsage>
              <tempUsage>
                  <tempUsage limit="100 mb"/>
              </tempUsage>
          </systemUsage>
      </systemUsage>
      -->
        <systemUsage>
            <systemUsage>
                <memoryUsage>
                    <memoryUsage limit="64 mb"/>
                </memoryUsage>
                <storeUsage>
                    <storeUsage limit="100 gb"/>
                </storeUsage>
                <tempUsage>
                    <tempUsage limit="50 gb"/>
                </tempUsage>
            </systemUsage>
        </systemUsage>

        <!--
            The transport connectors expose ActiveMQ over a given protocol to
            clients and other brokers. For more information, see:

            http://activemq.apache.org/configuring-transports.html
        -->
        <transportConnectors>
            <!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
            <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
            <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
        </transportConnectors>

        <!-- destroy the spring context on shutdown to stop jetty -->
        <shutdownHooks>
            <bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" />
        </shutdownHooks>
    </broker>
</beans>

但是，当我运行我的主类时，会显示此错误。我错过了配置中的任何内容吗？

Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://192.168.203.143:61616. Reason: java.net.ConnectException: Connection timed out: connect

【参考方案1】：

有类似的错误。 这是解决方案。

尝试使用您的 IP 地址连接到 borker 无法连接到代理 URL：tcp://192.168.203.143:61616。 上面提到的ip地址是与Example的系统相关的。

尝试为您的 ip 地址运行相同的代码。（在网络设置或命令“ipconfig”中了解您的 ipAddress） 无法连接到代理 URL：tcp://192.168.1.184:61616。

【参考方案2】：

您是否在 tcp://192.168.203.143:61616 上启动了 AMQ 代理？如果没有，那么启动它应该可以解决问题。

【讨论】：

我的 context.xml 上有一个代理工厂

根据我的理解，即使在声明工厂之后我们需要启动 AMQ 代理，请查看此链接，它提供了运行 AMQ 的更多详细信息。 shengwangi.blogspot.se/2014/10/…如果有任何问题请告诉我

有没有办法在嵌入式设置中自动启动 AMQ？

是的，有一种方法，例如，您还可以下载 activemq Web 控制台，用于从 tomcat 自动启动 activemq 实例。 repo1.maven.org/maven2/org/apache/activemq/activemq-web-console/…如果这有帮助，请告诉我，我会尝试寻找其他合适的选择

嗨，如果这个解决方案有帮助，或者您是否找到了更好的选择，请告诉我。