[jira] [Commented] (NIFI-3380) Multiple Versions of the Same Component

2017-03-25 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on NIFI-3380:
---

Commit f0a1c14f025f6013ed3667ea4470cd34846756d7 in nifi's branch 
refs/heads/master from [~bbende]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f0a1c14 ]

NIFI-3380 Fixing parent pom of nifi-standard-prioritizers to point to correct 
parent after moving under nifi-framework


> Multiple Versions of the Same Component
> ---
>
> Key: NIFI-3380
> URL: https://issues.apache.org/jira/browse/NIFI-3380
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Bryan Bende
>Assignee: Bryan Bende
> Fix For: 1.2.0
>
> Attachments: nifi-example-processors-nar-1.0.nar, 
> nifi-example-processors-nar-2.0.nar, nifi-example-service-api-nar-1.0.nar, 
> nifi-example-service-api-nar-2.0.nar, nifi-example-service-nar-1.0.nar, 
> nifi-example-service-nar-1.1.nar, nifi-example-service-nar-2.0.nar
>
>
> This ticket is to track the work for supporting multiple versions of the same 
> component within NiFi. The overall design for this feature is described in 
> detail at the following wiki page:
> https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension
> This ticket will track only the core NiFi work, and a separate ticket will be 
> created to track enhancements for the NAR Maven Plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-871) Site-to-Site does not report the actual hostname that it was trying to connect to when it fails to connect

2017-03-25 Thread Andre F de Miranda (JIRA) 

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

Andre F de Miranda commented on NIFI-871:
-

[~markap14] I suspect this bug has been fixed?

Logs:


{code:title=non-resolving hostname|borderStyle=solid}
2017-03-26 01:07:37,458 WARN [Remote Process Group 
05cb1c85-015b-1000-546b-caeee934f106: http://creepy.lab.fucs.org:5/ 
Thread-1] o.a.n.r.util.SiteToSiteRestApiClient Failed to get controller from 
http://creepy.lab.fucs.org:5/nifi-api due to java.net.UnknownHostException: 
creepy.lab.fucs.org: Name or service not known
{code}

{code:title=Connection timed-out|borderStyle=solid}
2017-03-26 01:12:13,927 WARN [Remote Process Group 05ceed19-015b-1000-c59a-bd1e5
0ecc2d0: http://192.168.1.203:58889 Thread-1] o.a.n.r.util.SiteToSiteRestApiClie
nt Failed to get controller from http://192.168.1.203:58889/nifi-api due to org.
apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.203:58889 [/192.1
68.1.203] failed: connect timed out
2017-03-26 01:12:13,928 WARN [Remote Process Group 05ceed19-015b-1000-c59a-bd1e5
0ecc2d0: http://192.168.1.203:58889 Thread-1] o.a.n.remote.StandardRemoteProcess
Group Unable to connect to RemoteProcessGroup[http://192.168.1.203:58889] due to
 org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.203:58889 [/
192.168.1.203] failed: connect timed out
2017-03-26 01:12:19,194 WARN [Timer-Driven Process Thread-8] 
o.a.n.r.util.SiteToSiteRestApiClient Failed to get controller from 
http://192.168.1.203:58889/nifi-api due to 
org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.203:58889 
[/192.168.1.203] failed: connect timed out
2017-03-26 01:12:19,194 WARN [Timer-Driven Process Thread-8] 
o.apache.nifi.controller.FlowController Unable to communicate with remote 
instance RemoteProcessGroup[http://192.168.1.203:58889] due to 
org.apache.nifi.controller.exception.CommunicationsException: Unable to 
communicate with Remote NiFi at URI http://192.168.1.203:58889 due to: Connect 
to 192.168.1.203:58889 [/192.168.1.203] failed: connect timed out
{code}

{code:title=connection refused|borderStyle=solid}
2017-03-26 01:14:47,248 WARN [Remote Process Group 
05d1b944-015b-1000-a1f9-8b2e244c6c2b: http://192.168.1.254:58889/ Thread-1] 
o.a.n.r.util.SiteToSiteRestApiClient Failed to get controller from 
http://192.168.1.254:58889/nifi-api due to 
org.apache.http.conn.HttpHostConnectException: Connect to 192.168.1.254:58889 
[/192.168.1.254] failed: Connection refused (Connection refused)
2017-03-26 01:14:47,248 WARN [Remote Process Group 
05d1b944-015b-1000-a1f9-8b2e244c6c2b: http://192.168.1.254:58889/ Thread-1] 
o.a.n.remote.StandardRemoteProcessGroup Unable to connect to 
RemoteProcessGroup[http://192.168.1.254:58889/] due to 
org.apache.http.conn.HttpHostConnectException: Connect to 192.168.1.254:58889 
[/192.168.1.254] failed: Connection refused (Connection refused)
2017-03-26 01:14:49,262 WARN [Timer-Driven Process Thread-3] 
o.a.n.r.util.SiteToSiteRestApiClient Failed to get controller from 
http://192.168.1.254:58889/nifi-api due to 
org.apache.http.conn.HttpHostConnectException: Connect to 192.168.1.254:58889 
[/192.168.1.254] failed: Connection refused (Connection refused)
2017-03-26 01:14:49,262 WARN [Timer-Driven Process Thread-3] 
o.apache.nifi.controller.FlowController Unable to communicate with remote 
instance RemoteProcessGroup[http://192.168.1.254:58889/] due to 
org.apache.nifi.controller.exception.CommunicationsException: Unable to 
communicate with Remote NiFi at URI http://192.168.1.254:58889/ due to: Connect 
to 192.168.1.254:58889 [/192.168.1.254] failed: Connection refused (Connection 
refused)
{code}

> Site-to-Site does not report the actual hostname that it was trying to 
> connect to when it fails to connect
> --
>
> Key: NIFI-871
> URL: https://issues.apache.org/jira/browse/NIFI-871
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Andre F de Miranda
>
> In testing the patch provided for NIFI-868, I set the nifi properties to 
> advertise the hostname as "otherhost". Site-to-Site, of course, failed to 
> connect, but rather indicating that it could not connect to otherhost, it 
> simply indicated that it was the RemoteProcessGroup connected to 
> http://localhost:8080/nifi. This is misleading because it leads the user to 
> believe that the Remote Process Group is having trouble connecting to 
> localhost, when in reality it is attempting to connect to "otherhost". We 
> should indicate which host we are connecting to when providing an error like 
> this.
> 2015-08-19 13:03:46,083 WARN [Timer-Driven Process Thread-10] 
>

[GitHub] nifi issue #1623: NIFI-55 - Log IP of clients generating expired holds and o...

2017-03-25 Thread trixpan 
Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1623
  
@joewitt Hopefully this addresses the targetted issue


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request #1623: NIFI-55 - Log IP of clients generating expired hold...

2017-03-25 Thread trixpan 
GitHub user trixpan opened a pull request:

https://github.com/apache/nifi/pull/1623

NIFI-55 - Log IP of clients generating expired holds and other cosmetic 
changes

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [X] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [X] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [X] ~~~Is your initial contribution a single, squashed commit?~~~

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [X] ~~~Have you written or updated unit tests to verify your changes?~~~
- [X] ~~~If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?~~~ 
- [X] ~~~If applicable, have you updated the LICENSE file, including the 
main LICENSE file under nifi-assembly?~~~
- [X] ~~~If applicable, have you updated the NOTICE file, including the 
main NOTICE file found under nifi-assembly?~~~
- [X] ~~~If adding new Properties, have you added .displayName in addition 
to .name (programmatic access) for each of the new properties?~~~

### For documentation related changes:
- [X] ~~~Have you ensured that format looks appropriate for the output in 
which it is rendered?~~~

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/trixpan/nifi NIFI-55

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1623.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1623


commit f817cc67cc86300149cfae79db4da616f51f84bf
Author: Andre F de Miranda 
Date:   2017-03-04T03:38:31Z

NIFI-55 - Use NetworkUtils.availablePorts instead of defining 
findAvailablePort

commit cdcd7e664ecac9315bd44d2a5f339f8ce5841924
Author: Andre F de Miranda 
Date:   2017-03-04T03:46:45Z

NIFI-55 - Replace odd reference to ListenTCP and replace with ListenHTTP

commit e79990a1c31b478d656a97072c1b12b3c801b75b
Author: Andre F de Miranda 
Date:   2017-03-25T13:21:02Z

NIFI-55 - Ensures ListenHTTP logs the source of an expired hold




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-55) ListenHTTP shoudl log who the sender of a FlowFile bundle is if the HOLD expires

2017-03-25 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on NIFI-55:


GitHub user trixpan opened a pull request:

https://github.com/apache/nifi/pull/1623

NIFI-55 - Log IP of clients generating expired holds and other cosmetic 
changes

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [X] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [X] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [X] ~~~Is your initial contribution a single, squashed commit?~~~

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [X] ~~~Have you written or updated unit tests to verify your changes?~~~
- [X] ~~~If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?~~~ 
- [X] ~~~If applicable, have you updated the LICENSE file, including the 
main LICENSE file under nifi-assembly?~~~
- [X] ~~~If applicable, have you updated the NOTICE file, including the 
main NOTICE file found under nifi-assembly?~~~
- [X] ~~~If adding new Properties, have you added .displayName in addition 
to .name (programmatic access) for each of the new properties?~~~

### For documentation related changes:
- [X] ~~~Have you ensured that format looks appropriate for the output in 
which it is rendered?~~~

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/trixpan/nifi NIFI-55

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1623.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1623


commit f817cc67cc86300149cfae79db4da616f51f84bf
Author: Andre F de Miranda 
Date:   2017-03-04T03:38:31Z

NIFI-55 - Use NetworkUtils.availablePorts instead of defining 
findAvailablePort

commit cdcd7e664ecac9315bd44d2a5f339f8ce5841924
Author: Andre F de Miranda 
Date:   2017-03-04T03:46:45Z

NIFI-55 - Replace odd reference to ListenTCP and replace with ListenHTTP

commit e79990a1c31b478d656a97072c1b12b3c801b75b
Author: Andre F de Miranda 
Date:   2017-03-25T13:21:02Z

NIFI-55 - Ensures ListenHTTP logs the source of an expired hold




> ListenHTTP shoudl log who the sender of a FlowFile bundle is if the HOLD 
> expires
> 
>
> Key: NIFI-55
> URL: https://issues.apache.org/jira/browse/NIFI-55
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Andre F de Miranda
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi-minifi pull request #78: MINIFI-251 - Added explicit Java runtime argum...

2017-03-25 Thread trixpan 
GitHub user trixpan opened a pull request:

https://github.com/apache/nifi-minifi/pull/78

MINIFI-251 - Added explicit Java runtime argument to default bootstra…

….conf to avoid blocking on VM deployment.

Thank you for submitting a contribution to Apache NiFi - MiNiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [X] Does your PR title start with MINIFI- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.

- [X] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [X] Is your initial contribution a single, squashed commit?

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi-minifi folder?
- [X]  ~~~Have you written or updated unit tests to verify your changes?~~~
- [X]  ~~~If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?~~~ 
- [X]  ~~~If applicable, have you updated the LICENSE file, including the 
main LICENSE file under minifi-assembly?~~~
- [X]  ~~~If applicable, have you updated the NOTICE file, including the 
main NOTICE file found under minifi-assembly?~~~

### For documentation related changes:
- [X] ~~~Have you ensured that format looks appropriate for the output in 
which it is rendered?~~~

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/trixpan/nifi-minifi MINIFI-251

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi-minifi/pull/78.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #78


commit 26f0cde711ecb34cf556b1e43d7246ea34c9e2da
Author: Andre F de Miranda 
Date:   2017-03-25T06:04:39Z

MINIFI-251 - Added explicit Java runtime argument to default bootstrap.conf 
to avoid blocking on VM deployment.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi pull request #77: MINIFI-251 - Added explicit Java runtime argum...

2017-03-25 Thread trixpan 
Github user trixpan closed the pull request at:

https://github.com/apache/nifi-minifi/pull/77


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi pull request #77: MINFI-251 - Added explicit Java runtime argume...

2017-03-25 Thread trixpan 
GitHub user trixpan opened a pull request:

https://github.com/apache/nifi-minifi/pull/77

MINFI-251 - Added explicit Java runtime argument to default bootstrap…

….conf to avoid blocking on VM deployment.

Thank you for submitting a contribution to Apache NiFi - MiNiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [X] Does your PR title start with MINIFI- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.

- [X] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [X] Is your initial contribution a single, squashed commit?

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi-minifi folder?
- [X]  ~~~Have you written or updated unit tests to verify your changes?~~~
- [X]  ~~~If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?~~~ 
- [X]  ~~~If applicable, have you updated the LICENSE file, including the 
main LICENSE file under minifi-assembly?~~~
- [X]  ~~~If applicable, have you updated the NOTICE file, including the 
main NOTICE file found under minifi-assembly?~~~

### For documentation related changes:
- [X] ~~~Have you ensured that format looks appropriate for the output in 
which it is rendered?~~~

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/trixpan/nifi-minifi MINIFI-251

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi-minifi/pull/77.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #77


commit f12a70c1c692f6d07ecf4eae13a9215552a3dd77
Author: Andre F de Miranda 
Date:   2017-03-25T06:04:39Z

MINFI-251 - Added explicit Java runtime argument to default bootstrap.conf 
to avoid blocking on VM deployment.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---