[
https://issues.apache.org/jira/browse/NIFI-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350560#comment-16350560
]
ASF GitHub Bot commented on NIFI-4834:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/2445
I ran this with an ActiveMQ instance in Docker and a [simple
flow](https://gist.github.com/alopresto/aec7eadd2ed8affd7be8e4056699e5f4) which
published JMS messages to a queue and then consumed them. It ran very well at
first, and I saw 10 threads on the ConsumeJMS once I configured it that way.
But after starting and stopping a few times, the ActiveMQ admin panel showed 30
consumers (3 times start/stopping 10 consumers) and no messages were being
consumed anymore. I have attached the bootstrap log which should have the
thread dump contents.
> 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
(v7.6.3#76005)
