Uploaded image for project: 'Qpid JMS'
  1. Qpid JMS
  2. QPIDJMS-358

Duplicate Messages delivered over AMQPS connectivity using QPID Jars

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Invalid
    • 0.11.1
    • None
    • qpid-jms-client
    • None

    Description

      Hello Team,

      We are using Apache QPID jars for AMQP  (JMS V1) to Azure Service Bus from IBM Integration Bus(IIB V9.0).

      We use below jars :-

      1. qpid-jms-client-0.11.1.jar
      2. proton-j-0.14.0.jar
      3. qpid-jms-discovery-0.11.1.jar
      4. slf4j-api-1.7.21.jar
      5. geronimo-jms_1.1_spec-1.1.1.jar

      Below is our connection URL :

      connectionfactory.qpidConnectionFactory = amqps://<server>:<port>?amqp.idleTimeout=150000&jms.username=<username>&jms.password=<password>&jms.receiveLocalOnly=true&jms.prefetchPolicy.all=1

      We connect to predefined subscriptions on an Azure Service Bus Topic.

      We have been using these jars for nearly a year now. Recently from past 2 weeks we are seeing some of the messages are delivered as duplicates with same JMS Message ID. Sometime same message is delivered 30-40 times within a second.

      Also we use same connection URL to different subscriptions (PROD and UAT) to same topic from our UAT and PROD servers. So we receive same payload in both the environments. And we have noticed that these duplicate counts vary from UAT to PROD.

       

      So looks like it can be some issue in the connection which is causing the duplicates. As we have had the upstream teams check complete data flow logic and we could not find any other place of duplicates.

       

      Please suggest how we can debug this issue to find its RCA and related fix.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Pooja Arora Pooja Arora
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: