You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Nissim Shiman (Jira)" <ji...@apache.org> on 2025/01/13 14:51:00 UTC

[jira] [Commented] (NIFI-14124) ConsumeJMS can cause JMS provider to have hung connections

    [ https://issues.apache.org/jira/browse/NIFI-14124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912559#comment-17912559 ] 

Nissim Shiman commented on NIFI-14124:
--------------------------------------

Issue has also been seen when topic is durable (on both ActiveMQ and Qpid) and when using queues (also on both ActiveMQ and Qpid)..

> ConsumeJMS can cause JMS provider to have hung connections 
> -----------------------------------------------------------
>
>                 Key: NIFI-14124
>                 URL: https://issues.apache.org/jira/browse/NIFI-14124
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Nissim Shiman
>            Assignee: Nissim Shiman
>            Priority: Major
>
> ConsumeJMS can cause JMS provider to have hung connections when NiFi is running as cluster, ConsumeJMS executes on primary node, is consuming from a topic and primary node is reassigned.
> This can be seen using Apache ActiveMQ 6.1.4 as JMS provider as well as Apache's Qpid JMS 2.6.1 (client) with Apache Qpid Broker-J (9.2.0) as JMS provider.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)