Tim Chermak created NIFI-6719:
---------------------------------
Summary: Changing JMS clientID causes durable subscription problems
Key: NIFI-6719
URL: https://issues.apache.org/jira/browse/NIFI-6719
Project: Apache NiFi
Issue Type: Task
Components: Core Framework
Affects Versions: 1.8.0
Environment: Linux CENTOS 7
Reporter: Tim Chermak
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 NiFi 3.12.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
