You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/01/05 10:36:06 UTC
[jira] [Resolved] (NIFI-8293) ConsumeJMS and PublishJMS performance
[ https://issues.apache.org/jira/browse/NIFI-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Villard resolved NIFI-8293.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.
> ConsumeJMS and PublishJMS performance
> -------------------------------------
>
> Key: NIFI-8293
> URL: https://issues.apache.org/jira/browse/NIFI-8293
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.11.4
> Reporter: Sergio Ignacio
> Priority: Major
> Labels: performance
>
> In our Nifi, we currently have some pipelines that connect to MQ queues. In these flows, we use the ConsumeJMS and PublishJMS processors.
> When we execute several pipelines at the same time, we see that the level of resource consumption increases.
> In the PublishJMS bibliography (https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.11.4/org.apache.nifi.jms. processors.PublishJMS /), there is a note regarding its memory consumption:
> "An instance of this component can cause high usage of this system resource. Multiple instances or high concurrency settings may result a degradation of performance."
> In the future, we will have many more new pipelines and the consumption impact on the Nifi servers will be even greater.
> Do you know any solution or configuration to help us deal with this?
> Thanks!
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)