[
https://issues.apache.org/jira/browse/NIFI-14124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael W Moser updated NIFI-14124:
-----------------------------------
Fix Version/s: 2.4.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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
> Fix For: 2.4.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> ConsumeJMS can cause the JMS provider to have hung connections. This occurs
> when NiFi is running as cluster and ConsumeJMS is executing on primary node,
> and primary node is reassigned.
> This is seen when consuming from topics (non-durable).
> 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)
