Score:0

Tomcat MQ Topic: Duplicate messages

gy flag

We are facing issues with duplicates on our tomcat setup. There are two tomcat nodes having each subscriber.

Below tomcat configuration on both tomcat nodes

Topic Connection

HOST="gbtstssis1.systems.uk.hsbc" PORT="15125" CHAN="RCSX.GB.C6" TRAN="1" SCPHS="TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384" QMGR="DGBLHSSIS1" CID="XCS-Equity-UAT-TOMCAT-53-Server" BSUB="SYSTEM.JMS.ND.GB_RCSX" CCSUB="SYSTEM.JMS.ND.CC.GB_RCSX" />

Destination Connection

Resource name="jms/xcsInTopicDSL_Ref" auth="Container" type="com.ibm.mq.jms.MQTopic" factory="com.ibm.mq.jms.MQTopicFactory" SCPHS="TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384" TOP="GLOBAL_ENV66/PRV_GDSL/+/IDSTORE" BDSUB="SYSTEM.JMS.D.GB_RCSX" CCDSUB="SYSTEM.JMS.D.CC.GB_RCSX"

BDSUB is broker durable subscription queue CCDSUB is broker cc durable subscription message queue

ClientID is different on both nodes, since it cannot be same. On WAS, there are no duplicate. I'm not sure, if there is any property missed on tomcat?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.