[
https://issues.apache.org/jira/browse/NIFI-7085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825374#comment-17825374
]
Michael W Moser commented on NIFI-7085:
---------------------------------------
When consuming a JMS queue, you can add more than 1 concurrent task to
ConsumeJMS to get the performance you need.
When consuming a JMS topic, if you add more than 1 concurrent task on a
non-durable, non-shared topic, then you receive duplicate messages and
performance does not improve. In this case, you cannot use more than 1 task.
I think I can improve ConsumeJMS by adding a Message Batch Size property, which
will allow the ability to consume more than 1 message per onTrigger().
As a note to anyone who reads this, recommend always setting ConsumeJMS Run
Schedule to 0 sec. If no message is available, then the Timeout property
controls how long to keep the timer-driven thread while waiting for a message
from the broker.
> Consume JMS is very slow
> ------------------------
>
> Key: NIFI-7085
> URL: https://issues.apache.org/jira/browse/NIFI-7085
> Project: Apache NiFi
> Issue Type: Improvement
> Environment: 1.8.0 nifi
> Reporter: naveen kumar saharan
> Priority: Minor
>
> ConsumeJMS as primary node consuming only 20 messages per second.
> If i do all nodes will it read duplicate?
> If i run multiple thread will it read as duplicate?
>
> We want to read 2000 messages per sec from Tibco jms.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
