[ https://issues.apache.org/jira/browse/NIFI-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koji Kawamura updated NIFI-5929: -------------------------------- Fix Version/s: 1.11.0 Resolution: Fixed Status: Resolved (was: Patch Available) Thanks [~vkcelik] for your contribution! I've added 'contributor' role to your JIRA account. Now you can assign to any NiFi JIRA issues. > Support for IBM MQ multi-instance queue managers (brokers) > ---------------------------------------------------------- > > Key: NIFI-5929 > URL: https://issues.apache.org/jira/browse/NIFI-5929 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions > Affects Versions: 1.0.0, 0.6.0, 0.7.0, 0.6.1, 1.1.0, 0.7.1, 1.2.0, 1.1.1, > 1.0.1, 1.3.0, 1.4.0, 0.7.4, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.7.1 > Reporter: Veli Kerim Celik > Assignee: Veli Kerim Celik > Priority: Major > Fix For: 1.11.0 > > Time Spent: 6h > Remaining Estimate: 0h > > Currently connections provided by JMSConnectionFactoryProvider controller > service can connect to just a single IBM MQ queue manager. This is > problematic when the queue manager is part of a [multi-instance queue > manager|https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q018140_.html] > setup and goes from active to standby. > The goal of this issue is to support multiple queue managers, detect > standby/broken instance and switch to active instance. This behavior is > already implemented in [official Java > library|https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.1.0/com.ibm.mq.javadoc.doc/WMQJMSClasses/com/ibm/mq/jms/MQConnectionFactory.html#setConnectionNameList_java.lang.String_] > and should be leveraged. > Syntax used to specify multiple queue managers: myhost01(1414),myhost02(1414) -- This message was sent by Atlassian Jira (v8.3.4#803005)