[ 
https://issues.apache.org/jira/browse/QPIDJMS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332429#comment-16332429
 ] 

Timothy Bish commented on QPIDJMS-358:
--------------------------------------

Given that you've not yet identified what's changed or what might be happening 
this really isn't the place to be asking for support, this would be better 
suited for the users mailing list.

That said you should start by testing what is going on with logging enabled and 
also frame tracing on to see what is happening at the wire level.  
Documentation for the version you are using can be found here which describes 
how to turn on the tracing: 
[http://qpid.apache.org/releases/qpid-jms-0.11.1/docs/index.html]

Since the client has been working for quite some time and this suddenly started 
to happen I'd be looking further up the chain to see what's changed as that is 
more likely to be the culprit.  If a bug is found though any fix would be made 
only in the latest release of the client so you'd be well served to update to 
the latest and begin testing on that version. 

> Duplicate Messages delivered over AMQPS connectivity using QPID Jars
> --------------------------------------------------------------------
>
>                 Key: QPIDJMS-358
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-358
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.11.1
>            Reporter: Pooja Arora
>            Priority: Critical
>
> 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 :-
>  # qpid-jms-client-0.11.1.jar
>  # proton-j-0.14.0.jar
>  # qpid-jms-discovery-0.11.1.jar
>  # slf4j-api-1.7.21.jar
>  # 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to