[
https://issues.apache.org/jira/browse/NIFI-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985182#comment-16985182
]
Gardella Juan Pablo commented on NIFI-4834:
-------------------------------------------
This enhancement introduced a critical bug, reported at
https://issues.apache.org/jira/browse/NIFI-6915.
> ConsumeJMS does not scale when given more than 1 thread
> -------------------------------------------------------
>
> Key: NIFI-4834
> URL: https://issues.apache.org/jira/browse/NIFI-4834
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.6.0
>
>
> When I run ConsumeJMS against a local broker, the performance is great.
> However, if I run against a broker that is running remotely with a 75 ms
> round trip time (i.e., somewhat high latency), then the performance is pretty
> poor, allowing me to receive only about 30-40 msgs/sec (1-2 MB/sec).
> Increasing the number of threads should result in multiple connections to the
> JMS Broker, which would provide better throughput. However, when I increase
> the number of Concurrent Tasks to 10, I see 10 consumers but only a single
> connection being created, so the throughput is no better (in fact it's a bit
> slower due to added lock contention).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
