gpt4 book ai didi

java - WSO2 ESB 无法调用 ActiveMQ

转载 作者:行者123 更新时间:2023-12-02 11:01:23 31 4
gpt4 key购买 nike

我对 WSO2 ESB 相当陌生。现在我必须在不使用 WSO2 消息代理的情况下将消息发送到 activemq 队列。

此时,我添加了 CARBON_HOME/lib 所需的所有 jar,并使用默认值启动了 activemq,并编辑了 axis2.xml 以启用 jms TransportSender

我的顺序如下:

<inSequence>
<log description="Log" level="full"/>
<call>
<endpoint>
<address uri="jms:/QueueName?transport.jms.DestinationType=queue&amp;transport.jms.ContentTypeProperty=Content-Type&amp;java.naming.provider.url=tcp://localhost:61616&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;transport.jms.ConnectionFactoryType=queue&amp;transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory"/>
</endpoint>
</call>
</inSequence

[2018-07-12 14:32:36,650] [] INFO - TimeoutHandler This engine will expire all callbacks after GLOBAL_TIMEOUT: 120 seconds, irrespective of the timeout action, after the specified or optional timeout [2018-07-12 14:33:07,253] [] ERROR - JMSSender Did not receive a JMS response within 30000 ms to destination : temp-queue://ID:NumbedPC-60591-1531395156918-1:1:1 with JMS correlation ID : ID:NumbedPC-60591-1531395156918-1:1:1:1:1 [2018-07-12 14:33:07,268] [] ERROR - Axis2Sender Unexpected error during sending message out org.apache.axis2.AxisFault: Did not receive a JMS response within 30000 ms to destination : temp-queue://ID:NumbedPC-60591-1531395156918-1:1:1 with JMS correlation ID : ID:NumbedPC-60591-1531395156918-1:1:1:1:1 at org.apache.axis2.transport.base.AbstractTransportSender.handleException(AbstractTransportSender.java:231) at org.apache.axis2.transport.jms.JMSSender.waitForResponseAndProcess(JMSSender.java:405) at org.apache.axis2.transport.jms.JMSSender.sendOverJMS(JMSSender.java:343) at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:200) at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442) at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185) at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149) at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:595) at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:83) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:548) at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:382) at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:65) at org.apache.synapse.mediators.builtin.CallMediator.handleNonBlockingCall(CallMediator.java:246) at org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:115) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59) at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158) at org.apache.synapse.rest.Resource.process(Resource.java:343) at org.apache.synapse.rest.API.process(API.java:399) at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRequestHandler.java:123) at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:101) at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:69) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:304) at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:78) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:326) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:372) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) [2018-07-12 14:33:07,289] [] WARN - EndpointContext Endpoint : AnonymousEndpoint with address jms:/QueueName?transport.jms.DestinationType=queue&transport.jms.ContentTypeProperty=Content-Type&java.naming.provider.url=tcp://localhost:61616&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&transport.jms.ConnectionFactoryType=queue&transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory will be marked SUSPENDED as it failed [2018-07-12 14:33:07,290] [] WARN - EndpointContext Suspending endpoint : AnonymousEndpoint with address jms:/QueueName?transport.jms.DestinationType=queue&transport.jms.ContentTypeProperty=Content-Type&java.naming.provider.url=tcp://localhost:61616&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&transport.jms.ConnectionFactoryType=queue&transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory - current suspend duration is : 30000ms - Next retry after : Thu Jul 12 14:33:37 MSK 2018

谁能告诉我我做错了什么?

最佳答案

您的设置假设发送 JMS 消息后,您将在最多 30 秒内收到 JMS 响应。因此,您的设置不是以“即发即忘”方式发送 JMS 消息,而是期望从另一端返回具有相同相关 ID 的响应。你可以清楚地看到这一点here, in line 368 .

检查如何配置<inSequence> <call>不要阻塞等待响应(如果需要的话)。或者,如果它是火,忘记设置 <inSequence>OUT_ONLY

您可以关注this example here .

关于java - WSO2 ESB 无法调用 ActiveMQ,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/51304851/

31 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com