You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Firenz (JIRA)" <ji...@apache.org> on 2018/11/15 22:24:00 UTC
[jira] [Created] (NIFI-5825) ConsumeJMS - Not using Clientid /
durable does not works
Firenz created NIFI-5825:
----------------------------
Summary: ConsumeJMS - Not using Clientid / durable does not works
Key: NIFI-5825
URL: https://issues.apache.org/jira/browse/NIFI-5825
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 1.8.0
Reporter: Firenz
I cannot make the ConsumeJMS 1.8.0 processor working as a durable. I set the client id, but it half-used. I'm using ActiveMQ (AmazonMQ).
I set :
* "sub" in Connection Client Id
* "true" in durable subscription
Result in ActiveMQ :
* NIFI creates in "Durable Topic Subscribers" "sub-<increment>" (like "sub-4" instead of "sub").
!image-2018-11-15-23-21-51-988.png!!image-2018-11-15-23-19-49-175.png!
I think the problem may be in AbstractJMSProcessor.java/buildTargetResource and we should have something like that :
{code:java}
String clientId = context.getProperty(CLIENT_ID).evaluateAttributeExpressions().getValue();
if (clientId != null) {
if (!durable){
// we have to generate a unique, dynamique, temp, client id
clientId = clientId + "-" + clientIdCounter.getAndIncrement();
}
cachingFactory.setClientId(clientId);
}
{code}
But dunno how to get this "durable" prop in the Abstract during the "OnTrigger" stuff...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)