Uploaded image for project: 'Qpid Dispatch'
  1. Qpid Dispatch
  2. DISPATCH-2350

Facing issues after upgrading qpid-dispatch-router and tools from 1.16 to 1.18

    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.18.0
    • None
    • Protocol Adaptors, Routing Engine
    • None

    • DEV

      PREPROD

    Description

      Hello,

      Below is what our application and messaging architecture looks like. 

      We have  a Microservice --> nlb --> qpid ---> amq brokers (Master/slave)

      It looks that when we upgraded qpid dispatch router and tool from 1.16 to 1.18 we observed that the client(application) is producing messages and messages are not getting consumed and instead they are routing to delivering count, they stay in delivering count until we restart our brokers or qpid then only they look to be consumed. We are having to do multiple restarts of qpid and apache activemq in order for messages to get consumed and get clear from delivering count. 

       

      We are not seeing any failures or exception in qpid nor amq to triage this issue further. We are suspecting that maybe apache activemq 2.18 isn;t compatible with qpid dispatch 1.18. Could that be leading us to this issue? the only exception we saw in the logs is " javax.jms.JMSException: Delivery failed: released by receiver". Below is the log snippet. We are seeing this exception with qpid-dispatch-router and tools with 1.16 as well as 1.18 version. 

       

      We would love any feedback or any suggestions if anyone have regarding these two versions of activemq and qpid. Thanks 

       

       

      Error processing exchange. Exchange[]. Caused by: [org.springframework.jms.UncategorizedJmsException - Uncategorized exception occurred during JMS processing; nested exception is javax.jms.JMSException: Delivery failed: released by receiver]
      org.springframework.jms.UncategorizedJmsException: Uncategorized exception occurred during JMS processing; nested exception is javax.jms.JMSException: Delivery failed: released by receiver
       at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:311) ~[spring-jms-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
       at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:185) ~[spring-jms-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
       at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:507) ~[spring-jms-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
       at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.send(JmsConfiguration.java:525) ~[camel-jms-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.jms.JmsProducer.doSend(JmsProducer.java:438) ~[camel-jms-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.jms.JmsProducer.processInOnly(JmsProducer.java:392) ~[camel-jms-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.jms.JmsProducer.process(JmsProducer.java:155) ~[camel-jms-3.4.0.jar!/:3.4.0]
       at org.apache.camel.impl.engine.DeferProducer.process(DeferProducer.java:62) ~[camel-base-3.4.0.jar!/:3.4.0]
       at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:286) ~[camel-base-3.4.0.jar!/:3.4.0]
       at org.apache.camel.processor.UnitOfWorkProducer.process(UnitOfWorkProducer.java:56) ~[camel-base-3.4.0.jar!/:3.4.0]
       at org.apache.camel.processor.EventNotifierProducer.process(EventNotifierProducer.java:71) ~[camel-base-3.4.0.jar!/:3.4.0]
       at org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83) ~[camel-base-3.4.0.jar!/:3.4.0]
       at org.apache.camel.support.DefaultAsyncProducer.process(DefaultAsyncProducer.java:40) ~[camel-support-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.bean.AbstractCamelInvocationHandler$1.call(AbstractCamelInvocationHandler.java:188) ~[camel-bean-3.4.0.jar!/:3.4.0]
       at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_322]
       at org.apache.camel.component.bean.AbstractCamelInvocationHandler.doInvoke(AbstractCamelInvocationHandler.java:206) ~[camel-bean-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.bean.AbstractCamelInvocationHandler.invokeProxy(AbstractCamelInvocationHandler.java:168) ~[camel-bean-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.bean.CamelInvocationHandler.doInvokeProxy(CamelInvocationHandler.java:44) ~[camel-bean-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.bean.AbstractCamelInvocationHandler.invoke(AbstractCamelInvocationHandler.java:81) ~[camel-bean-3.4.0.jar!/:3.4.0]
       at com.sun.proxy.$Proxy110.sendDispatch(Unknown Source) ~[na:na]
       at com.od.eai.framework.core.dispatch.processor.ReportDispatch.sendDispatch(ReportDispatch.java:25) ~[eai-fw-core-3.0.0-SNAPSHOT.jar!/:na]
       at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source) ~[na:na]
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_322]
       at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_322]
       at org.apache.camel.support.ObjectHelper.invokeMethodSafe(ObjectHelper.java:209) ~[camel-support-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.bean.MethodInfo.invoke(MethodInfo.java:421) ~[camel-bean-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.bean.MethodInfo$1.doProceed(MethodInfo.java:242) ~[camel-bean-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.bean.MethodInfo$1.proceed(MethodInfo.java:213) ~[camel-bean-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.bean.AbstractBeanProcessor.process(AbstractBeanProcessor.java:154) ~[camel-bean-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:56) ~[camel-bean-3.4.0.jar!/:3.4.0]
       at org.apache.camel.support.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:93) ~[camel-support-3.4.0.jar!/:3.4.0]
       at org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$SimpleTask.run(RedeliveryErrorHandler.java:395) ~[camel-base-3.4.0.jar!/:3.4.0]
       at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:148) ~[camel-base-3.4.0.jar!/:3.4.0]
       at org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:60) ~[camel-base-3.4.0.jar!/:3.4.0]
       at org.apache.camel.processor.Pipeline.process(Pipeline.java:147) ~[camel-base-3.4.0.jar!/:3.4.0]
       at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:286) ~[camel-base-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.seda.SedaConsumer.sendToConsumers(SedaConsumer.java:271) [camel-seda-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.seda.SedaConsumer.doRun(SedaConsumer.java:185) [camel-seda-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:130) [camel-seda-3.4.0.jar!/:3.4.0]
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_322]
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_322]
       at java.lang.Thread.run(Thread.java:750) [na:1.8.0_322]
      Caused by: javax.jms.JMSException: Delivery failed: released by receiver
       at org.apache.qpid.jms.provider.ProviderException.toJMSException(ProviderException.java:34) ~[qpid-jms-client-0.52.0.jar!/:na]
       at org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80) ~[qpid-jms-client-0.52.0.jar!/:na]
       at org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112) ~[qpid-jms-client-0.52.0.jar!/:na]
       at org.apache.qpid.jms.JmsConnection.send(JmsConnection.java:778) ~[qpid-jms-client-0.52.0.jar!/:na]
       at org.apache.qpid.jms.JmsNoTxTransactionContext.send(JmsNoTxTransactionContext.java:37) ~[qpid-jms-client-0.52.0.jar!/:na]
       at org.apache.qpid.jms.JmsSession.send(JmsSession.java:964) ~[qpid-jms-client-0.52.0.jar!/:na]
       at org.apache.qpid.jms.JmsSession.send(JmsSession.java:843) ~[qpid-jms-client-0.52.0.jar!/:na]
       at org.apache.qpid.jms.JmsMessageProducer.sendMessage(JmsMessageProducer.java:252) ~[qpid-jms-client-0.52.0.jar!/:na]
       at org.apache.qpid.jms.JmsMessageProducer.send(JmsMessageProducer.java:200) ~[qpid-jms-client-0.52.0.jar!/:na]
       at org.apache.activemq.jms.pool.PooledProducer.send(PooledProducer.java:95) ~[activemq-jms-pool-5.15.12.jar!/:5.15.12]
       at org.apache.activemq.jms.pool.PooledProducer.send(PooledProducer.java:66) ~[activemq-jms-pool-5.15.12.jar!/:5.15.12]
       at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:634) ~[spring-jms-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
       at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.doSend(JmsConfiguration.java:623) ~[camel-jms-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.doSendToDestination(JmsConfiguration.java:562) ~[camel-jms-3.4.0.jar!/:3.4.0]
       at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.lambda$send$0(JmsConfiguration.java:527) ~[camel-jms-3.4.0.jar!/:3.4.0]
       at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:504) ~[spring-jms-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
       ... 39 common frames omitted

      Attachments

        Activity

          People

            Unassigned Unassigned
            ekta-awasthi Ekta
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: