[jira] [Commented] (NIFI-2716) Allow NiFi to manage embedded JMS Brokers
[ https://issues.apache.org/jira/browse/NIFI-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809648#comment-15809648 ] ASF GitHub Bot commented on NIFI-2716: -- Github user olegz closed the pull request at: https://github.com/apache/nifi/pull/1118 > Allow NiFi to manage embedded JMS Brokers > - > > Key: NIFI-2716 > URL: https://issues.apache.org/jira/browse/NIFI-2716 > Project: Apache NiFi > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky > > Several community members expressed interest in NiFi acting as a JMS Broker > to avoid deploying and managing external JMS Brokers. While implementing JMS > Broker from scratch would be rather complex, using embedded capabilities of > some OS JMS Broker implementations (e.g., ActiveMQ) together with native > capabilities of NiFi (i.e., Processor and/or Controller Service) could prove > to be a very valuable feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2716) Allow NiFi to manage embedded JMS Brokers
[ https://issues.apache.org/jira/browse/NIFI-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15809647#comment-15809647 ] ASF GitHub Bot commented on NIFI-2716: -- Github user olegz commented on the issue: https://github.com/apache/nifi/pull/1118 There seems to be no traction at the moment, closing for now. > Allow NiFi to manage embedded JMS Brokers > - > > Key: NIFI-2716 > URL: https://issues.apache.org/jira/browse/NIFI-2716 > Project: Apache NiFi > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky > > Several community members expressed interest in NiFi acting as a JMS Broker > to avoid deploying and managing external JMS Brokers. While implementing JMS > Broker from scratch would be rather complex, using embedded capabilities of > some OS JMS Broker implementations (e.g., ActiveMQ) together with native > capabilities of NiFi (i.e., Processor and/or Controller Service) could prove > to be a very valuable feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2716) Allow NiFi to manage embedded JMS Brokers
[ https://issues.apache.org/jira/browse/NIFI-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15633804#comment-15633804 ] ASF GitHub Bot commented on NIFI-2716: -- Github user olegz commented on the issue: https://github.com/apache/nifi/pull/1118 @brosander all is good now > Allow NiFi to manage embedded JMS Brokers > - > > Key: NIFI-2716 > URL: https://issues.apache.org/jira/browse/NIFI-2716 > Project: Apache NiFi > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky > > Several community members expressed interest in NiFi acting as a JMS Broker > to avoid deploying and managing external JMS Brokers. While implementing JMS > Broker from scratch would be rather complex, using embedded capabilities of > some OS JMS Broker implementations (e.g., ActiveMQ) together with native > capabilities of NiFi (i.e., Processor and/or Controller Service) could prove > to be a very valuable feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2716) Allow NiFi to manage embedded JMS Brokers
[ https://issues.apache.org/jira/browse/NIFI-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15633754#comment-15633754 ] ASF GitHub Bot commented on NIFI-2716: -- Github user olegz commented on the issue: https://github.com/apache/nifi/pull/1118 @brosander I'll fix it. Thanks for pointing it out > Allow NiFi to manage embedded JMS Brokers > - > > Key: NIFI-2716 > URL: https://issues.apache.org/jira/browse/NIFI-2716 > Project: Apache NiFi > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky > > Several community members expressed interest in NiFi acting as a JMS Broker > to avoid deploying and managing external JMS Brokers. While implementing JMS > Broker from scratch would be rather complex, using embedded capabilities of > some OS JMS Broker implementations (e.g., ActiveMQ) together with native > capabilities of NiFi (i.e., Processor and/or Controller Service) could prove > to be a very valuable feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2716) Allow NiFi to manage embedded JMS Brokers
[ https://issues.apache.org/jira/browse/NIFI-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15633398#comment-15633398 ] ASF GitHub Bot commented on NIFI-2716: -- Github user brosander commented on the issue: https://github.com/apache/nifi/pull/1118 @olegz it looks like this PR has merge issues now > Allow NiFi to manage embedded JMS Brokers > - > > Key: NIFI-2716 > URL: https://issues.apache.org/jira/browse/NIFI-2716 > Project: Apache NiFi > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky > > Several community members expressed interest in NiFi acting as a JMS Broker > to avoid deploying and managing external JMS Brokers. While implementing JMS > Broker from scratch would be rather complex, using embedded capabilities of > some OS JMS Broker implementations (e.g., ActiveMQ) together with native > capabilities of NiFi (i.e., Processor and/or Controller Service) could prove > to be a very valuable feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
