[NIFI-6719] Changing JMS clientID causes durable subscription problems

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 1.8.0
• Component/s: Extensions
• Labels: patch
• Environment: Linux CENTOS 7
• Assignee: Unassigned
• Reporter: Tim Chermak
• Created: 26/Sep/19 14:00
• Updated: 19/Jan/20 15:08
• Resolved: 19/Jan/20 15:08

Description

Using ConsumeJMS we set clientID = nificid, durable = true and subscription = nifidur. After several tests where we received messages and stopped/started the processor between tests. We had the following durables for TIBCO:

• infrastructure.itx.monitoring nificid-5:nifidur N <offline> 40 8.8 kb
• infrastructure.itx.monitoring nificid-6:nifidur N <offline> 20 4.4 kb
• infrastructure.itx.monitoring nificid-4:nifidur N <offline> 60 13.2 kb

The clientID used was modified with an appended "-<digit>", and the digit increased with each restart. The test with ActiveMQ had the same problem.

 

The resulting offline durables collect messages. The durable name is a combination of the clientID and the subscription name and NiFi has to remember and reuse the same durable name after a restart of the processor. The same problem was found and fixed in an older version before 1.x.

 

Issue Links

• duplicates: NIFI-6915 Jms Durable non shared subscription is broken