[jira] [Commented] (NIFI-12343) PutElasticsearchJson exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852215#comment-17852215
]
Gregory M. Foreman commented on NIFI-12343:
---
[~Chris S] thank you for doing this!
> PutElasticsearchJson exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12343
> URL: https://issues.apache.org/jira/browse/NIFI-12343
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2, 2.0.0-M2
>Reporter: Gregory M. Foreman
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 2.0.0-M4
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
>
> PutElasticsearchJson throws an exception when reading JSON documents that
> contain string fields over 20 MB:
> {code:java}
> PutElasticsearchJson[id=] No FlowFiles successfully parsed for sending to
> Elasticsearch
> PutElasticsearchJson[id=] Could not read FlowFile content valid JSON.:
> com.fasterxml.jackson.core.exc.StreamConstraintsException: String length
> (20050553) exceeds the maximum length (2000)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12343) PutElasticsearchJson exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-12343:
--
Affects Version/s: 2.0.0-M2
> PutElasticsearchJson exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12343
> URL: https://issues.apache.org/jira/browse/NIFI-12343
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2, 2.0.0-M2
>Reporter: Gregory M. Foreman
>Priority: Major
>
>
> PutElasticsearchJson throws an exception when reading JSON documents that
> contain string fields over 20 MB:
> {code:java}
> PutElasticsearchJson[id=] No FlowFiles successfully parsed for sending to
> Elasticsearch
> PutElasticsearchJson[id=] Could not read FlowFile content valid JSON.:
> com.fasterxml.jackson.core.exc.StreamConstraintsException: String length
> (20050553) exceeds the maximum length (2000)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12875) RestLookupService not handling HTTP 4xx/5xx error codes
[ https://issues.apache.org/jira/browse/NIFI-12875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory M. Foreman updated NIFI-12875: -- Status: Patch Available (was: Open) > RestLookupService not handling HTTP 4xx/5xx error codes > --- > > Key: NIFI-12875 > URL: https://issues.apache.org/jira/browse/NIFI-12875 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 2.0.0-M2 >Reporter: Gregory M. Foreman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The RestLookupService service does not handle HTTP error codes correctly. If > the web service being consumed returns a 4xx or 5xx error code, the > RestLookupService service ignores the error and passes the response content > to the record reader, causing unexpected exception reporting. > Example: a web service that communicates with clients via JSON is behind a > proxy. The proxy returns a 502 error and responds with HTML content > describing the error. The RestLookupService uses a JsonTreeReader reader and > attempts to parse the HTML characters. This leads to it throwing an > exception that it was unable to parse the '<' character. The real reason is > the proxy is sending back a 502 error, but this detail is hidden. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12875) RestLookupService not handling HTTP 4xx/5xx error codes
Gregory M. Foreman created NIFI-12875: - Summary: RestLookupService not handling HTTP 4xx/5xx error codes Key: NIFI-12875 URL: https://issues.apache.org/jira/browse/NIFI-12875 Project: Apache NiFi Issue Type: Bug Affects Versions: 2.0.0-M2 Reporter: Gregory M. Foreman The RestLookupService service does not handle HTTP error codes correctly. If the web service being consumed returns a 4xx or 5xx error code, the RestLookupService service ignores the error and passes the response content to the record reader, causing unexpected exception reporting. Example: a web service that communicates with clients via JSON is behind a proxy. The proxy returns a 502 error and responds with HTML content describing the error. The RestLookupService uses a JsonTreeReader reader and attempts to parse the HTML characters. This leads to it throwing an exception that it was unable to parse the '<' character. The real reason is the proxy is sending back a 502 error, but this detail is hidden. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (NIFI-12854) PutS3Object: expand support for generating metadata
[ https://issues.apache.org/jira/browse/NIFI-12854 ] Gregory M. Foreman deleted comment on NIFI-12854: --- was (Author: gforeman02): Hello [~markap14], thanks for posting. Yes, the existing method (dynamic properties) requires knowing what the user metadata keys will be in advance. My client has a scenario where one flow has metadata key A and another that has key B and this is only known by reading the flowfile attributes. It would be great for the processor to work in the same way it does for tags. > PutS3Object: expand support for generating metadata > --- > > Key: NIFI-12854 > URL: https://issues.apache.org/jira/browse/NIFI-12854 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M2 >Reporter: Gregory M. Foreman >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > The PutS3Object processor currently supports adding user metadata to objects > via dynamic properties. Add support for using FlowFile attributes to > generate user metadata. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12854) PutS3Object: expand support for generating metadata
[ https://issues.apache.org/jira/browse/NIFI-12854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824154#comment-17824154 ] Gregory M. Foreman commented on NIFI-12854: --- Hello [~markap14], thanks for posting. Yes, the existing method (dynamic properties) requires knowing what the user metadata keys will be in advance. My client has a scenario where one flow has metadata key A and another that has key B and this is only known by reading the flowfile attributes. It would be great for the processor to work in the same way it does for tags. > PutS3Object: expand support for generating metadata > --- > > Key: NIFI-12854 > URL: https://issues.apache.org/jira/browse/NIFI-12854 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M2 >Reporter: Gregory M. Foreman >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The PutS3Object processor currently supports adding user metadata to objects > via dynamic properties. Add support for using FlowFile attributes to > generate user metadata. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12854) PutS3Object: expand support for generating metadata
[ https://issues.apache.org/jira/browse/NIFI-12854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory M. Foreman updated NIFI-12854: -- Description: The PutS3Object processor currently supports adding user metadata to objects via dynamic properties. Add support for using FlowFile attributes to generate user metadata. (was: The PutS3Object processor currently supports adding metadata to objects via dynamic properties. Add support for using FlowFile attributes to generate S3 metadata.) > PutS3Object: expand support for generating metadata > --- > > Key: NIFI-12854 > URL: https://issues.apache.org/jira/browse/NIFI-12854 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M2 >Reporter: Gregory M. Foreman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The PutS3Object processor currently supports adding user metadata to objects > via dynamic properties. Add support for using FlowFile attributes to > generate user metadata. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12854) PutS3Object: expand support for generating metadata
[ https://issues.apache.org/jira/browse/NIFI-12854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory M. Foreman updated NIFI-12854: -- Status: Patch Available (was: Open) > PutS3Object: expand support for generating metadata > --- > > Key: NIFI-12854 > URL: https://issues.apache.org/jira/browse/NIFI-12854 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M2 >Reporter: Gregory M. Foreman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The PutS3Object processor currently supports adding metadata to objects via > dynamic properties. Add support for using FlowFile attributes to generate S3 > metadata. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12854) PutS3Object: expand support for generating metadata
Gregory M. Foreman created NIFI-12854: - Summary: PutS3Object: expand support for generating metadata Key: NIFI-12854 URL: https://issues.apache.org/jira/browse/NIFI-12854 Project: Apache NiFi Issue Type: Improvement Affects Versions: 2.0.0-M2 Reporter: Gregory M. Foreman The PutS3Object processor currently supports adding metadata to objects via dynamic properties. Add support for using FlowFile attributes to generate S3 metadata. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12300) OAuth2 support in RestLookupService
[ https://issues.apache.org/jira/browse/NIFI-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory M. Foreman updated NIFI-12300: -- Status: Patch Available (was: Open) > OAuth2 support in RestLookupService > --- > > Key: NIFI-12300 > URL: https://issues.apache.org/jira/browse/NIFI-12300 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M2, 1.23.2 >Reporter: Gregory M. Foreman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Enable the RestLookupService to use StandardOauth2AccessTokenProvider to > support REST services that require oauth2 tokens to access. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12300) OAuth2 support in RestLookupService
[ https://issues.apache.org/jira/browse/NIFI-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory M. Foreman updated NIFI-12300: -- Affects Version/s: 2.0.0-M2 > OAuth2 support in RestLookupService > --- > > Key: NIFI-12300 > URL: https://issues.apache.org/jira/browse/NIFI-12300 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.23.2, 2.0.0-M2 >Reporter: Gregory M. Foreman >Priority: Major > > Enable the RestLookupService to use StandardOauth2AccessTokenProvider to > support REST services that require oauth2 tokens to access. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12300) OAuth2 support in RestLookupService
[ https://issues.apache.org/jira/browse/NIFI-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory M. Foreman updated NIFI-12300: -- Issue Type: Improvement (was: New Feature) > OAuth2 support in RestLookupService > --- > > Key: NIFI-12300 > URL: https://issues.apache.org/jira/browse/NIFI-12300 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.23.2 >Reporter: Gregory M. Foreman >Priority: Major > > Enable the RestLookupService to use StandardOauth2AccessTokenProvider to > support REST services that require oauth2 tokens to access. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12292) PutElasticsearchHttp exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman resolved NIFI-12292.
---
Resolution: Won't Fix
> PutElasticsearchHttp exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12292
> URL: https://issues.apache.org/jira/browse/NIFI-12292
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2
>Reporter: Gregory M. Foreman
>Priority: Major
>
> PutElasticsearchHttp throws an exception when reading JSON documents that
> contain string fields over 20 MB:
> {code:java}
> PutElasticsearchHttp[id=] Flow file content is not valid JSON, penalizing
> and transferring to failure. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12292) PutElasticsearchHttp exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784614#comment-17784614
]
Gregory M. Foreman commented on NIFI-12292:
---
Thanks for clarifying. I will close this ticket. Opened NIFI-12343.
> PutElasticsearchHttp exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12292
> URL: https://issues.apache.org/jira/browse/NIFI-12292
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2
>Reporter: Gregory M. Foreman
>Priority: Major
>
> PutElasticsearchHttp throws an exception when reading JSON documents that
> contain string fields over 20 MB:
> {code:java}
> PutElasticsearchHttp[id=] Flow file content is not valid JSON, penalizing
> and transferring to failure. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12343) PutElasticsearchJson exception with JSON strings over 20 MB
Gregory M. Foreman created NIFI-12343:
-
Summary: PutElasticsearchJson exception with JSON strings over 20
MB
Key: NIFI-12343
URL: https://issues.apache.org/jira/browse/NIFI-12343
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Affects Versions: 1.23.2
Reporter: Gregory M. Foreman
PutElasticsearchJson throws an exception when reading JSON documents that
contain string fields over 20 MB:
{code:java}
PutElasticsearchJson[id=] No FlowFiles successfully parsed for sending to
Elasticsearch
PutElasticsearchJson[id=] Could not read FlowFile content valid JSON.:
com.fasterxml.jackson.core.exc.StreamConstraintsException: String length
(20050553) exceeds the maximum length (2000)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12292) PutElasticsearchHttp exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784561#comment-17784561
]
Gregory M. Foreman commented on NIFI-12292:
---
[~bbende] do you happen to know if PutElasticsearchHttp (this one) was
addressed?
> PutElasticsearchHttp exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12292
> URL: https://issues.apache.org/jira/browse/NIFI-12292
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2
>Reporter: Gregory M. Foreman
>Priority: Major
>
> PutElasticsearchHttp throws an exception when reading JSON documents that
> contain string fields over 20 MB:
> {code:java}
> PutElasticsearchHttp[id=] Flow file content is not valid JSON, penalizing
> and transferring to failure. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12292) PutElasticsearchHttp exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784500#comment-17784500
]
Gregory M. Foreman commented on NIFI-12292:
---
[~bbende] I reviewed:
[NIFI-12323 Configure StreamReadConstraints on the ObjectMapper used b… by
bbende · Pull Request #7985 · apache/nifi ·
GitHub|https://github.com/apache/nifi/pull/7985/files#diff-aa64084868d7f234108c98fa298f7e7980400dc02c4ebe07166c0a7005e5f386R157]
I like the solution. Would support it being applied to the processors impacted
by the Jackson library change.
> PutElasticsearchHttp exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12292
> URL: https://issues.apache.org/jira/browse/NIFI-12292
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2
>Reporter: Gregory M. Foreman
>Priority: Major
>
> PutElasticsearchHttp throws an exception when reading JSON documents that
> contain string fields over 20 MB:
> {code:java}
> PutElasticsearchHttp[id=] Flow file content is not valid JSON, penalizing
> and transferring to failure. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12300) OAuth2 support in RestLookupService
Gregory M. Foreman created NIFI-12300: - Summary: OAuth2 support in RestLookupService Key: NIFI-12300 URL: https://issues.apache.org/jira/browse/NIFI-12300 Project: Apache NiFi Issue Type: New Feature Affects Versions: 1.23.2 Reporter: Gregory M. Foreman Enable the RestLookupService to use StandardOauth2AccessTokenProvider to support REST services that require oauth2 tokens to access. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12292) PutElasticsearchHttp exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-12292:
--
Component/s: Extensions
(was: Core Framework)
> PutElasticsearchHttp exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12292
> URL: https://issues.apache.org/jira/browse/NIFI-12292
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2
>Reporter: Gregory M. Foreman
>Priority: Major
>
> PutElasticsearchHttp throws an exception when reading JSON documents that
> contain string fields over 20 MB:
> {code:java}
> PutElasticsearchHttp[id=] Flow file content is not valid JSON, penalizing
> and transferring to failure. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12292) PutElasticsearchHttp exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-12292:
--
Description:
PutElasticsearchHttp throws an exception when reading JSON documents that
contain string fields over 20 MB:
{code:java}
PutElasticsearchHttp[id=] Flow file content is not valid JSON, penalizing
and transferring to failure. {code}
was:
PutElasticsearchHttp throws an exception when reading documents that contain
JSON strings over 20 MB:
{code:java}
PutElasticsearchHttp[id=] Flow file content is not valid JSON, penalizing
and transferring to failure. {code}
> PutElasticsearchHttp exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12292
> URL: https://issues.apache.org/jira/browse/NIFI-12292
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.23.2
>Reporter: Gregory M. Foreman
>Priority: Major
>
> PutElasticsearchHttp throws an exception when reading JSON documents that
> contain string fields over 20 MB:
> {code:java}
> PutElasticsearchHttp[id=] Flow file content is not valid JSON, penalizing
> and transferring to failure. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12292) PutElasticsearchHttp exception with JSON strings over 20 MB
Gregory M. Foreman created NIFI-12292:
-
Summary: PutElasticsearchHttp exception with JSON strings over 20
MB
Key: NIFI-12292
URL: https://issues.apache.org/jira/browse/NIFI-12292
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 1.23.2
Reporter: Gregory M. Foreman
PutElasticsearchHttp throws an exception when reading documents that contain
JSON strings over 20 MB:
{code:java}
PutElasticsearchHttp[id=] Flow file content is not valid JSON, penalizing
and transferring to failure. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11917) RPM build not being maintained - not working - not in testing chain - consider removal
[
https://issues.apache.org/jira/browse/NIFI-11917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769708#comment-17769708
]
Gregory M. Foreman commented on NIFI-11917:
---
[~joewitt] , having Nifi in the EPEL repo would remove the need to run the
maven build at all (for us anyway). I think the only thing needed by EPEL is
the binary version of Nifi, so testing should be easy and would be performed by
EPEL project resources. If none of the options is possible, then we will just
create the rpm on our own.
> RPM build not being maintained - not working - not in testing chain -
> consider removal
> --
>
> Key: NIFI-11917
> URL: https://issues.apache.org/jira/browse/NIFI-11917
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.23.0
> Environment: Linux
>Reporter: Gregory M. Foreman
>Assignee: Joe Witt
>Priority: Major
> Fix For: 2.latest
>
>
> Nifi 1.23.0 is unable to build from source when using the rpm profile setting.
> This command:
> {code:java}
> JAVA_OPTS="-Xms128m -Xmx4g"
> MAVEN_OPTS="-Dorg.slf4j.simpleLogger.defaultLogLevel=ERROR -Xms1024m
> -Xmx3076m -XX:MaxPermSize=256m"
> mvn -T C2.0 --batch-mode -Prpm -DskipTests clean install
> {code}
> produces the following error:
> {code:java}
> [ERROR] Failed to execute goal
> org.codehaus.mojo:rpm-maven-plugin:2.2.0:attached-rpm (build-bin-rpm) on
> project nifi-toolkit-assembly: Source location
> /root/test/nifi-1.23.0/nifi-toolkit/nifi-toolkit-assembly/target/nifi-toolkit-1.23.0-bin/nifi-toolkit-1.23.0/LICENSE
> does not exist -> [Help 1]{code}
> The path above ends at:
> /root/test2/nifi/nifi-toolkit/nifi-toolkit-assembly/target/
> There is a zip file within it:
> nifi-toolkit-1.23.0-bin.zip
> It seems like this unzip was missed.
> Environment info:
> {code:bash}
> mvn -version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 1.8.0_372, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el7_9.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.95.1.el7.x86_64", arch: "amd64",
> family: "unix"{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11917) Building RPM from source producers error
[
https://issues.apache.org/jira/browse/NIFI-11917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769349#comment-17769349
]
Gregory M. Foreman commented on NIFI-11917:
---
[~joewitt] I anticipate us continuing to use RPM deployments into the
foreseeable future.
Is there any support for migrating the capability to something like EPEL?
> Building RPM from source producers error
>
>
> Key: NIFI-11917
> URL: https://issues.apache.org/jira/browse/NIFI-11917
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.23.0
> Environment: Linux
>Reporter: Gregory M. Foreman
>Priority: Major
>
> Nifi 1.23.0 is unable to build from source when using the rpm profile setting.
> This command:
> {code:java}
> JAVA_OPTS="-Xms128m -Xmx4g"
> MAVEN_OPTS="-Dorg.slf4j.simpleLogger.defaultLogLevel=ERROR -Xms1024m
> -Xmx3076m -XX:MaxPermSize=256m"
> mvn -T C2.0 --batch-mode -Prpm -DskipTests clean install
> {code}
> produces the following error:
> {code:java}
> [ERROR] Failed to execute goal
> org.codehaus.mojo:rpm-maven-plugin:2.2.0:attached-rpm (build-bin-rpm) on
> project nifi-toolkit-assembly: Source location
> /root/test/nifi-1.23.0/nifi-toolkit/nifi-toolkit-assembly/target/nifi-toolkit-1.23.0-bin/nifi-toolkit-1.23.0/LICENSE
> does not exist -> [Help 1]{code}
> The path above ends at:
> /root/test2/nifi/nifi-toolkit/nifi-toolkit-assembly/target/
> There is a zip file within it:
> nifi-toolkit-1.23.0-bin.zip
> It seems like this unzip was missed.
> Environment info:
> {code:bash}
> mvn -version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 1.8.0_372, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el7_9.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.95.1.el7.x86_64", arch: "amd64",
> family: "unix"{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12127) EvaluateJsonPath exception with JSON strings over 20 MB
[
https://issues.apache.org/jira/browse/NIFI-12127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-12127:
--
Description:
EvaluateJsonPath throws an exception when reading documents that contain JSON
strings over 20 MB:
{code:java}
2023-09-25 20:21:21,219 ERROR [Timer-Driven Process Thread-2]
o.a.n.p.standard.EvaluateJsonPath
EvaluateJsonPath[id=cdeb7d6b-018a-1000--a48fe458] FlowFile
StandardFlowFileRecord[uuid=f79f7846-18a7-4f04-8049-bc30abb17bcf,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1695672616030-8, container=content1,
section=8], offset=0,
length=27962063],offset=0,name=954d4b05-3748-45ac-964f-89a09bc30f27,size=27962063]
did not have valid JSON content. {code}
was:
EvaluateJsonPath throws an exception when processing JSON strings over 20 MB:
{code:java}
2023-09-25 20:21:21,219 ERROR [Timer-Driven Process Thread-2]
o.a.n.p.standard.EvaluateJsonPath
EvaluateJsonPath[id=cdeb7d6b-018a-1000--a48fe458] FlowFile
StandardFlowFileRecord[uuid=f79f7846-18a7-4f04-8049-bc30abb17bcf,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1695672616030-8, container=content1,
section=8], offset=0,
length=27962063],offset=0,name=954d4b05-3748-45ac-964f-89a09bc30f27,size=27962063]
did not have valid JSON content. {code}
> EvaluateJsonPath exception with JSON strings over 20 MB
> ---
>
> Key: NIFI-12127
> URL: https://issues.apache.org/jira/browse/NIFI-12127
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2
>Reporter: Gregory M. Foreman
>Priority: Major
>
> EvaluateJsonPath throws an exception when reading documents that contain JSON
> strings over 20 MB:
> {code:java}
> 2023-09-25 20:21:21,219 ERROR [Timer-Driven Process Thread-2]
> o.a.n.p.standard.EvaluateJsonPath
> EvaluateJsonPath[id=cdeb7d6b-018a-1000--a48fe458] FlowFile
> StandardFlowFileRecord[uuid=f79f7846-18a7-4f04-8049-bc30abb17bcf,claim=StandardContentClaim
> [resourceClaim=StandardResourceClaim[id=1695672616030-8, container=content1,
> section=8], offset=0,
> length=27962063],offset=0,name=954d4b05-3748-45ac-964f-89a09bc30f27,size=27962063]
> did not have valid JSON content. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12127) EvaluateJsonPath exception with JSON strings over 20 MB
Gregory M. Foreman created NIFI-12127:
-
Summary: EvaluateJsonPath exception with JSON strings over 20 MB
Key: NIFI-12127
URL: https://issues.apache.org/jira/browse/NIFI-12127
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Affects Versions: 1.23.2
Reporter: Gregory M. Foreman
EvaluateJsonPath throws an exception when processing JSON strings over 20 MB:
{code:java}
2023-09-25 20:21:21,219 ERROR [Timer-Driven Process Thread-2]
o.a.n.p.standard.EvaluateJsonPath
EvaluateJsonPath[id=cdeb7d6b-018a-1000--a48fe458] FlowFile
StandardFlowFileRecord[uuid=f79f7846-18a7-4f04-8049-bc30abb17bcf,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1695672616030-8, container=content1,
section=8], offset=0,
length=27962063],offset=0,name=954d4b05-3748-45ac-964f-89a09bc30f27,size=27962063]
did not have valid JSON content. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12117) JoltTransformJSON exception with JSON strings over 20MB
[
https://issues.apache.org/jira/browse/NIFI-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-12117:
--
Summary: JoltTransformJSON exception with JSON strings over 20MB (was:
JoltTransformJSON exception with json strings over 20MB)
> JoltTransformJSON exception with JSON strings over 20MB
> ---
>
> Key: NIFI-12117
> URL: https://issues.apache.org/jira/browse/NIFI-12117
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2
>Reporter: Gregory M. Foreman
>Priority: Major
>
> The following exception is thrown when attempting to process JSON string
> content greater than 20 MB:
> {code:java}
> JoltTransformJSON[id=a9fca990-018a-1000--6e33ec9a] JSON parsing
> failed for FlowFile[filename=07ddb61f-a581-4de9-932d-4cbdf3ef2b52]:
> com.bazaarvoice.jolt.exception.JsonUnmarshalException: Unable to unmarshal
> JSON to an Object.- Caused by:
> com.fasterxml.jackson.core.exc.StreamConstraintsException: String length
> (20051112) exceeds the maximum length (2000) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12117) JoltTransformJSON exception with json strings over 20MB
[
https://issues.apache.org/jira/browse/NIFI-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-12117:
--
Component/s: Extensions
> JoltTransformJSON exception with json strings over 20MB
> ---
>
> Key: NIFI-12117
> URL: https://issues.apache.org/jira/browse/NIFI-12117
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.23.2
>Reporter: Gregory M. Foreman
>Priority: Major
>
> The following exception is thrown when attempting to process JSON string
> content greater than 20 MB:
> {code:java}
> JoltTransformJSON[id=a9fca990-018a-1000--6e33ec9a] JSON parsing
> failed for FlowFile[filename=07ddb61f-a581-4de9-932d-4cbdf3ef2b52]:
> com.bazaarvoice.jolt.exception.JsonUnmarshalException: Unable to unmarshal
> JSON to an Object.- Caused by:
> com.fasterxml.jackson.core.exc.StreamConstraintsException: String length
> (20051112) exceeds the maximum length (2000) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12117) JoltTransformJSON exception with json strings over 20MB
Gregory M. Foreman created NIFI-12117:
-
Summary: JoltTransformJSON exception with json strings over 20MB
Key: NIFI-12117
URL: https://issues.apache.org/jira/browse/NIFI-12117
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 1.23.2
Reporter: Gregory M. Foreman
The following exception is thrown when attempting to process JSON string
content greater than 20 MB:
{code:java}
JoltTransformJSON[id=a9fca990-018a-1000--6e33ec9a] JSON parsing failed
for FlowFile[filename=07ddb61f-a581-4de9-932d-4cbdf3ef2b52]:
com.bazaarvoice.jolt.exception.JsonUnmarshalException: Unable to unmarshal JSON
to an Object.- Caused by:
com.fasterxml.jackson.core.exc.StreamConstraintsException: String length
(20051112) exceeds the maximum length (2000) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11917) Building RPM from source producers error
[
https://issues.apache.org/jira/browse/NIFI-11917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754202#comment-17754202
]
Gregory M. Foreman edited comment on NIFI-11917 at 8/14/23 5:39 PM:
This works around the issue by skipping the offending module:
{code:java}
mvn -T C2.0 --batch-mode -DskipTests -Prpm -pl
'!nifi-toolkit/nifi-toolkit-assembly' clean install {code}
was (Author: gforeman02):
This works around the issue by skipping the offending pom:
{code:java}
mvn -T C2.0 --batch-mode -DskipTests -Prpm -pl
'!nifi-toolkit/nifi-toolkit-assembly' clean install {code}
> Building RPM from source producers error
>
>
> Key: NIFI-11917
> URL: https://issues.apache.org/jira/browse/NIFI-11917
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.23.0
> Environment: Linux
>Reporter: Gregory M. Foreman
>Priority: Major
>
> Nifi 1.23.0 is unable to build from source when using the rpm profile setting.
> This command:
> {code:java}
> JAVA_OPTS="-Xms128m -Xmx4g"
> MAVEN_OPTS="-Dorg.slf4j.simpleLogger.defaultLogLevel=ERROR -Xms1024m
> -Xmx3076m -XX:MaxPermSize=256m"
> mvn -T C2.0 --batch-mode -Prpm -DskipTests clean install
> {code}
> produces the following error:
> {code:java}
> [ERROR] Failed to execute goal
> org.codehaus.mojo:rpm-maven-plugin:2.2.0:attached-rpm (build-bin-rpm) on
> project nifi-toolkit-assembly: Source location
> /root/test/nifi-1.23.0/nifi-toolkit/nifi-toolkit-assembly/target/nifi-toolkit-1.23.0-bin/nifi-toolkit-1.23.0/LICENSE
> does not exist -> [Help 1]{code}
> The path above ends at:
> /root/test2/nifi/nifi-toolkit/nifi-toolkit-assembly/target/
> There is a zip file within it:
> nifi-toolkit-1.23.0-bin.zip
> It seems like this unzip was missed.
> Environment info:
> {code:bash}
> mvn -version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 1.8.0_372, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el7_9.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.95.1.el7.x86_64", arch: "amd64",
> family: "unix"{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11917) Building RPM from source producers error
[
https://issues.apache.org/jira/browse/NIFI-11917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754202#comment-17754202
]
Gregory M. Foreman commented on NIFI-11917:
---
This works around the issue by skipping the offending pom:
{code:java}
mvn -T C2.0 --batch-mode -DskipTests -Prpm -pl
'!nifi-toolkit/nifi-toolkit-assembly' clean install {code}
> Building RPM from source producers error
>
>
> Key: NIFI-11917
> URL: https://issues.apache.org/jira/browse/NIFI-11917
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.23.0
> Environment: Linux
>Reporter: Gregory M. Foreman
>Priority: Major
>
> Nifi 1.23.0 is unable to build from source when using the rpm profile setting.
> This command:
> {code:java}
> JAVA_OPTS="-Xms128m -Xmx4g"
> MAVEN_OPTS="-Dorg.slf4j.simpleLogger.defaultLogLevel=ERROR -Xms1024m
> -Xmx3076m -XX:MaxPermSize=256m"
> mvn -T C2.0 --batch-mode -Prpm -DskipTests clean install
> {code}
> produces the following error:
> {code:java}
> [ERROR] Failed to execute goal
> org.codehaus.mojo:rpm-maven-plugin:2.2.0:attached-rpm (build-bin-rpm) on
> project nifi-toolkit-assembly: Source location
> /root/test/nifi-1.23.0/nifi-toolkit/nifi-toolkit-assembly/target/nifi-toolkit-1.23.0-bin/nifi-toolkit-1.23.0/LICENSE
> does not exist -> [Help 1]{code}
> The path above ends at:
> /root/test2/nifi/nifi-toolkit/nifi-toolkit-assembly/target/
> There is a zip file within it:
> nifi-toolkit-1.23.0-bin.zip
> It seems like this unzip was missed.
> Environment info:
> {code:bash}
> mvn -version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 1.8.0_372, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el7_9.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.95.1.el7.x86_64", arch: "amd64",
> family: "unix"{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11917) Building RPM from source producers error
[
https://issues.apache.org/jira/browse/NIFI-11917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-11917:
--
Component/s: (was: Configuration)
> Building RPM from source producers error
>
>
> Key: NIFI-11917
> URL: https://issues.apache.org/jira/browse/NIFI-11917
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.23.0
> Environment: Linux
>Reporter: Gregory M. Foreman
>Priority: Major
>
> Nifi 1.23.0 is unable to build from source when using the rpm profile setting.
> This command:
> {code:java}
> JAVA_OPTS="-Xms128m -Xmx4g"
> MAVEN_OPTS="-Dorg.slf4j.simpleLogger.defaultLogLevel=ERROR -Xms1024m
> -Xmx3076m -XX:MaxPermSize=256m"
> mvn -T C2.0 --batch-mode -Prpm -DskipTests clean install
> {code}
> produces the following error:
> {code:java}
> [ERROR] Failed to execute goal
> org.codehaus.mojo:rpm-maven-plugin:2.2.0:attached-rpm (build-bin-rpm) on
> project nifi-toolkit-assembly: Source location
> /root/test/nifi-1.23.0/nifi-toolkit/nifi-toolkit-assembly/target/nifi-toolkit-1.23.0-bin/nifi-toolkit-1.23.0/LICENSE
> does not exist -> [Help 1]{code}
> The path above ends at:
> /root/test2/nifi/nifi-toolkit/nifi-toolkit-assembly/target/
> There is a zip file within it:
> nifi-toolkit-1.23.0-bin.zip
> It seems like this unzip was missed.
> Environment info:
> {code:bash}
> mvn -version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 1.8.0_372, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el7_9.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.95.1.el7.x86_64", arch: "amd64",
> family: "unix"{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-11917) Building RPM from source producers error
Gregory M. Foreman created NIFI-11917:
-
Summary: Building RPM from source producers error
Key: NIFI-11917
URL: https://issues.apache.org/jira/browse/NIFI-11917
Project: Apache NiFi
Issue Type: Bug
Components: Configuration
Affects Versions: 1.23.0
Environment: Linux
Reporter: Gregory M. Foreman
Nifi 1.23.0 is unable to build from source when using the rpm profile setting.
This command:
{code:java}
JAVA_OPTS="-Xms128m -Xmx4g"
MAVEN_OPTS="-Dorg.slf4j.simpleLogger.defaultLogLevel=ERROR -Xms1024m -Xmx3076m
-XX:MaxPermSize=256m"
mvn -T C2.0 --batch-mode -Prpm -DskipTests clean install
{code}
produces the following error:
{code:java}
[ERROR] Failed to execute goal
org.codehaus.mojo:rpm-maven-plugin:2.2.0:attached-rpm (build-bin-rpm) on
project nifi-toolkit-assembly: Source location
/root/test/nifi-1.23.0/nifi-toolkit/nifi-toolkit-assembly/target/nifi-toolkit-1.23.0-bin/nifi-toolkit-1.23.0/LICENSE
does not exist -> [Help 1]{code}
The path above ends at:
/root/test2/nifi/nifi-toolkit/nifi-toolkit-assembly/target/
There is a zip file within it:
nifi-toolkit-1.23.0-bin.zip
It seems like this unzip was missed.
Environment info:
{code:bash}
mvn -version
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /opt/maven
Java version: 1.8.0_372, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el7_9.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.95.1.el7.x86_64", arch: "amd64",
family: "unix"{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-9656) Publish an alternative Java 11 docker image
[ https://issues.apache.org/jira/browse/NIFI-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17521177#comment-17521177 ] Gregory M. Foreman commented on NIFI-9656: -- My client has custom nar's that rely on Java 11 jar libraries. Addressing this issue would simplify deployments for us. If it is trivial to do two images during the deployment, it would be appreciated. Additionally, Nifi 1.16 now supports Java 17 (NIFI-9280), so having Java 8, 11, and 17 images would be even better. > Publish an alternative Java 11 docker image > --- > > Key: NIFI-9656 > URL: https://issues.apache.org/jira/browse/NIFI-9656 > Project: Apache NiFi > Issue Type: Wish > Components: Docker >Affects Versions: 1.15.3 > Environment: Docker >Reporter: Christoph Nölle >Priority: Minor > > There have been requests before to update the official Docker image to Java > 11 (such as [NIFI-9188|https://issues.apache.org/jira/browse/NIFI-9188]). As > I understand, this would be a breaking change for many users, though, and > therefore has been postponed for Nifi 2.0. On the other hand, it would be > quite desirable if one could use Java 11 features in custom processors > (without maintaining a custom Docker image). > A solution could be to keep Java 8 for the default image (e.g. tagged > "1.15.3" = latest) and provide a second image, e.g. "1.15.3-openjdk-11". The > Dockerfile has already been adapted to support building with a Java 11 base > image in [https://github.com/apache/nifi/pull/4460]. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9525) RPM build does not produce working Nifi
[
https://issues.apache.org/jira/browse/NIFI-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-9525:
-
Status: Patch Available (was: Open)
> RPM build does not produce working Nifi
> ---
>
> Key: NIFI-9525
> URL: https://issues.apache.org/jira/browse/NIFI-9525
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.15.1, 1.15.2
> Environment: Centos 7
>Reporter: Gregory M. Foreman
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Maven RPM build fails to produce an operational Nifi installation.
>
>
>
>
> {code:bash}
> $ mvn -version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.49.1.el7.x86_64", arch: "amd64",
> family: "unix"
> $ mvn clean install -Prpm -DskipTests
> $ yum localinstall
> nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm
> $ /opt/nifi/nifi-1.15.1/bin/nifi.sh start
> nifi.sh: JAVA_HOME not set; results may vary
> Java home:
> NiFi home: /opt/nifi/nifi-1.15.1
> Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/nifi/security/util/TlsConfiguration
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at
> org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124)
> at org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247)
> at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.nifi.security.util.TlsConfiguration
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 15 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (NIFI-9525) RPM build does not produce working Nifi
[
https://issues.apache.org/jira/browse/NIFI-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468200#comment-17468200
]
Gregory M. Foreman commented on NIFI-9525:
--
[~joewitt] Yes, happy to assist.
> RPM build does not produce working Nifi
> ---
>
> Key: NIFI-9525
> URL: https://issues.apache.org/jira/browse/NIFI-9525
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.15.1, 1.15.2
> Environment: Centos 7
>Reporter: Gregory M. Foreman
>Priority: Major
>
> Maven RPM build fails to produce an operational Nifi installation.
>
>
>
>
> {code:bash}
> $ mvn -version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.49.1.el7.x86_64", arch: "amd64",
> family: "unix"
> $ mvn clean install -Prpm -DskipTests
> $ yum localinstall
> nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm
> $ /opt/nifi/nifi-1.15.1/bin/nifi.sh start
> nifi.sh: JAVA_HOME not set; results may vary
> Java home:
> NiFi home: /opt/nifi/nifi-1.15.1
> Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/nifi/security/util/TlsConfiguration
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at
> org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124)
> at org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247)
> at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.nifi.security.util.TlsConfiguration
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 15 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (NIFI-9525) RPM build does not produce working Nifi
[
https://issues.apache.org/jira/browse/NIFI-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-9525:
-
Affects Version/s: 1.15.2
> RPM build does not produce working Nifi
> ---
>
> Key: NIFI-9525
> URL: https://issues.apache.org/jira/browse/NIFI-9525
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.15.1, 1.15.2
> Environment: Centos 7
>Reporter: Gregory M. Foreman
>Priority: Major
>
> Maven RPM build fails to produce an operational Nifi installation.
>
>
>
>
> {code:bash}
> $ mvn -version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.49.1.el7.x86_64", arch: "amd64",
> family: "unix"
> $ mvn clean install -Prpm -DskipTests
> $ yum localinstall
> nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm
> $ /opt/nifi/nifi-1.15.1/bin/nifi.sh start
> nifi.sh: JAVA_HOME not set; results may vary
> Java home:
> NiFi home: /opt/nifi/nifi-1.15.1
> Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/nifi/security/util/TlsConfiguration
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at
> org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124)
> at org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247)
> at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.nifi.security.util.TlsConfiguration
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 15 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (NIFI-9525) RPM build does not produce working Nifi
[
https://issues.apache.org/jira/browse/NIFI-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468168#comment-17468168
]
Gregory M. Foreman edited comment on NIFI-9525 at 1/3/22, 7:44 PM:
---
The lib directories differ between the maven build and the rpm package. The
nifi-assembly pom contains a number of include/exclude package statements to
assemble the lib directory for the rpm. I replaced the existing mapping for
the lib directory with the entry below and it ran fine:
{code:xml}
/opt/nifi/nifi-${project.version}/lib
${project.build.directory}/nifi-${project.version}-bin/nifi-${project.version}/lib
{code}
Is this an option? Or is the include/exclude approach used for a specific
reason?
was (Author: gforeman02):
The lib directories differ between the maven build and the rpm package. The
nifi-assembly pom contains a number of include/exclude package statements to
assemble the lib directory for the rpm. I replaced the existing mapping for
the lib directory with the entry below and it ran fine:
{code:XML}
/opt/nifi/nifi-${project.version}/lib
${project.build.directory}/nifi-${project.version}-bin/nifi-${project.version}/lib
{code}
Is this an option? Or are the include/exclude approach used for a specific
reason?
> RPM build does not produce working Nifi
> ---
>
> Key: NIFI-9525
> URL: https://issues.apache.org/jira/browse/NIFI-9525
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.15.1
> Environment: Centos 7
>Reporter: Gregory M. Foreman
>Priority: Major
>
> Maven RPM build fails to produce an operational Nifi installation.
>
>
>
>
> {code:bash}
> $ mvn -version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.49.1.el7.x86_64", arch: "amd64",
> family: "unix"
> $ mvn clean install -Prpm -DskipTests
> $ yum localinstall
> nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm
> $ /opt/nifi/nifi-1.15.1/bin/nifi.sh start
> nifi.sh: JAVA_HOME not set; results may vary
> Java home:
> NiFi home: /opt/nifi/nifi-1.15.1
> Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/nifi/security/util/TlsConfiguration
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at
> org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124)
> at org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247)
> at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.nifi.security.util.TlsConfiguration
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 15 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (NIFI-9525) RPM build does not produce working Nifi
[
https://issues.apache.org/jira/browse/NIFI-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468168#comment-17468168
]
Gregory M. Foreman commented on NIFI-9525:
--
The lib directories differ between the maven build and the rpm package. The
nifi-assembly pom contains a number of include/exclude package statements to
assemble the lib directory for the rpm. I replaced the existing mapping for
the lib directory with the entry below and it ran fine:
{code:XML}
/opt/nifi/nifi-${project.version}/lib
${project.build.directory}/nifi-${project.version}-bin/nifi-${project.version}/lib
{code}
Is this an option? Or are the include/exclude approach used for a specific
reason?
> RPM build does not produce working Nifi
> ---
>
> Key: NIFI-9525
> URL: https://issues.apache.org/jira/browse/NIFI-9525
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.15.1
> Environment: Centos 7
>Reporter: Gregory M. Foreman
>Priority: Major
>
> Maven RPM build fails to produce an operational Nifi installation.
>
>
>
>
> {code:bash}
> $ mvn -version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1160.49.1.el7.x86_64", arch: "amd64",
> family: "unix"
> $ mvn clean install -Prpm -DskipTests
> $ yum localinstall
> nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm
> $ /opt/nifi/nifi-1.15.1/bin/nifi.sh start
> nifi.sh: JAVA_HOME not set; results may vary
> Java home:
> NiFi home: /opt/nifi/nifi-1.15.1
> Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/nifi/security/util/TlsConfiguration
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at
> org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124)
> at org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247)
> at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.nifi.security.util.TlsConfiguration
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 15 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (NIFI-9525) RPM build does not produce working Nifi
[
https://issues.apache.org/jira/browse/NIFI-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-9525:
-
Description:
Maven RPM build fails to produce an operational Nifi installation.
{code:bash}
$ mvn -version
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /opt/maven
Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1160.49.1.el7.x86_64", arch: "amd64",
family: "unix"
$ mvn clean install -Prpm -DskipTests
$ yum localinstall
nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm
$ /opt/nifi/nifi-1.15.1/bin/nifi.sh start
nifi.sh: JAVA_HOME not set; results may vary
Java home:
NiFi home: /opt/nifi/nifi-1.15.1
Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/nifi/security/util/TlsConfiguration
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at
org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124)
at org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247)
at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289)
Caused by: java.lang.ClassNotFoundException:
org.apache.nifi.security.util.TlsConfiguration
at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
... 15 more
{code}
was:
Maven RPM build fails to produce an operational Nifi installation.
{{{}$ mvn -version{}}}{{{}Apache Maven 3.8.4
(9b656c72d54e5bacbed989b64718c159fe39b537){}}}{{{}Maven home:
/opt/maven{}}}{{{}Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre{}}}{{{}Default
locale: en_US, platform encoding: UTF-8{}}}{{{}OS name: "linux", version:
"3.10.0-1160.49.1.el7.x86_64", arch: "amd64", family: "unix"{}}}
{{$ mvn clean install -Prpm -DskipTests}}
{{$ yum localinstall
nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm}}
{{{}$ /opt/nifi/nifi-1.15.1/bin/nifi.sh start{}}}{{{}nifi.sh: JAVA_HOME not
set; results may vary{}}}
{{Java home: }}{{NiFi home: /opt/nifi/nifi-1.15.1}}
{{Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf}}
{{{}Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/nifi/security/util/TlsConfiguration{}}}{{{}at
java.lang.ClassLoader.defineClass1(Native Method){}}}{{{}at
java.lang.ClassLoader.defineClass(ClassLoader.java:756){}}}{{{}at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142){}}}{{{}at
java.net.URLClassLoader.defineClass(URLClassLoader.java:473){}}}{{{}at
java.net.URLClassLoader.access$100(URLClassLoader.java:74){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:369){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:363){}}}{{{}at
java.security.AccessController.doPrivileged(Native Method){}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:362){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:351){}}}{{{}at
org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289){}}}{{{}Caused by:
java.lang.ClassNotFoundException:
org.apache.nifi.security.util.TlsConfiguration{}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:387){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352){}}}{{{}at
[jira] [Updated] (NIFI-9525) RPM build does not produce working Nifi
[
https://issues.apache.org/jira/browse/NIFI-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-9525:
-
Description:
Maven RPM build fails to produce an operational Nifi installation.
{{{}$ mvn -version{}}}{{{}Apache Maven 3.8.4
(9b656c72d54e5bacbed989b64718c159fe39b537){}}}{{{}Maven home:
/opt/maven{}}}{{{}Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre{}}}{{{}Default
locale: en_US, platform encoding: UTF-8{}}}{{{}OS name: "linux", version:
"3.10.0-1160.49.1.el7.x86_64", arch: "amd64", family: "unix"{}}}
{{}}
{{$ mvn clean install -Prpm -DskipTests}}
{{}}
{{$ yum localinstall
nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm}}
{{}}
{{{}$ /opt/nifi/nifi-1.15.1/bin/nifi.sh start{}}}{{{}nifi.sh: JAVA_HOME not
set; results may vary{}}}
{{Java home: }}{{NiFi home: /opt/nifi/nifi-1.15.1}}
{{Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf}}
{{{}Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/nifi/security/util/TlsConfiguration{}}}{{{}at
java.lang.ClassLoader.defineClass1(Native Method){}}}{{{}at
java.lang.ClassLoader.defineClass(ClassLoader.java:756){}}}{{{}at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142){}}}{{{}at
java.net.URLClassLoader.defineClass(URLClassLoader.java:473){}}}{{{}at
java.net.URLClassLoader.access$100(URLClassLoader.java:74){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:369){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:363){}}}{{{}at
java.security.AccessController.doPrivileged(Native Method){}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:362){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:351){}}}{{{}at
org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289){}}}{{{}Caused by:
java.lang.ClassNotFoundException:
org.apache.nifi.security.util.TlsConfiguration{}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:387){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:351){}}}{{{}... 15 more{}}}
was:
Maven RPM build fails to produce an operational Nifi installation.
{{{}$ mvn -version{}}}{{{}Apache Maven 3.8.4
(9b656c72d54e5bacbed989b64718c159fe39b537){}}}{{{}Maven home:
/opt/maven{}}}{{{}Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre{}}}{{{}Default
locale: en_US, platform encoding: UTF-8{}}}{{{}OS name: "linux", version:
"3.10.0-1160.49.1.el7.x86_64", arch: "amd64", family: "unix"{}}}
{{$ mvn clean install -Prpm -DskipTests}}
{{$ yum localinstall
nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm}}
{{{}$ /opt/nifi/nifi-1.15.1/bin/nifi.sh start{}}}{{{}nifi.sh: JAVA_HOME not
set; results may vary{}}}
{{Java home: }}{{NiFi home: /opt/nifi/nifi-1.15.1}}
{{Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf}}
{{{}Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/nifi/security/util/TlsConfiguration{}}}{{{}at
java.lang.ClassLoader.defineClass1(Native Method){}}}{{{}at
java.lang.ClassLoader.defineClass(ClassLoader.java:756){}}}{{{}at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142){}}}{{{}at
java.net.URLClassLoader.defineClass(URLClassLoader.java:473){}}}{{{}at
java.net.URLClassLoader.access$100(URLClassLoader.java:74){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:369){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:363){}}}{{{}at
java.security.AccessController.doPrivileged(Native Method){}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:362){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:351){}}}{{{}at
org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289){}}}{{{}Caused by:
java.lang.ClassNotFoundException:
org.apache.nifi.security.util.TlsConfiguration{}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:387){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
[jira] [Updated] (NIFI-9525) RPM build does not produce working Nifi
[
https://issues.apache.org/jira/browse/NIFI-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory M. Foreman updated NIFI-9525:
-
Description:
Maven RPM build fails to produce an operational Nifi installation.
{{{}$ mvn -version{}}}{{{}Apache Maven 3.8.4
(9b656c72d54e5bacbed989b64718c159fe39b537){}}}{{{}Maven home:
/opt/maven{}}}{{{}Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre{}}}{{{}Default
locale: en_US, platform encoding: UTF-8{}}}{{{}OS name: "linux", version:
"3.10.0-1160.49.1.el7.x86_64", arch: "amd64", family: "unix"{}}}
{{$ mvn clean install -Prpm -DskipTests}}
{{$ yum localinstall
nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm}}
{{{}$ /opt/nifi/nifi-1.15.1/bin/nifi.sh start{}}}{{{}nifi.sh: JAVA_HOME not
set; results may vary{}}}
{{Java home: }}{{NiFi home: /opt/nifi/nifi-1.15.1}}
{{Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf}}
{{{}Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/nifi/security/util/TlsConfiguration{}}}{{{}at
java.lang.ClassLoader.defineClass1(Native Method){}}}{{{}at
java.lang.ClassLoader.defineClass(ClassLoader.java:756){}}}{{{}at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142){}}}{{{}at
java.net.URLClassLoader.defineClass(URLClassLoader.java:473){}}}{{{}at
java.net.URLClassLoader.access$100(URLClassLoader.java:74){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:369){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:363){}}}{{{}at
java.security.AccessController.doPrivileged(Native Method){}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:362){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:351){}}}{{{}at
org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289){}}}{{{}Caused by:
java.lang.ClassNotFoundException:
org.apache.nifi.security.util.TlsConfiguration{}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:387){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:351){}}}{{{}... 15 more{}}}
was:
Maven RPM build fails to produce an operational Nifi installation.
{{{}$ mvn -version{}}}{{{}Apache Maven 3.8.4
(9b656c72d54e5bacbed989b64718c159fe39b537){}}}{{{}Maven home:
/opt/maven{}}}{{{}Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre{}}}{{{}Default
locale: en_US, platform encoding: UTF-8{}}}{{{}OS name: "linux", version:
"3.10.0-1160.49.1.el7.x86_64", arch: "amd64", family: "unix"{}}}
{{}}
{{$ mvn clean install -Prpm -DskipTests}}
{{}}
{{$ yum localinstall
nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm}}
{{}}
{{{}$ /opt/nifi/nifi-1.15.1/bin/nifi.sh start{}}}{{{}nifi.sh: JAVA_HOME not
set; results may vary{}}}
{{Java home: }}{{NiFi home: /opt/nifi/nifi-1.15.1}}
{{Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf}}
{{{}Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/nifi/security/util/TlsConfiguration{}}}{{{}at
java.lang.ClassLoader.defineClass1(Native Method){}}}{{{}at
java.lang.ClassLoader.defineClass(ClassLoader.java:756){}}}{{{}at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142){}}}{{{}at
java.net.URLClassLoader.defineClass(URLClassLoader.java:473){}}}{{{}at
java.net.URLClassLoader.access$100(URLClassLoader.java:74){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:369){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:363){}}}{{{}at
java.security.AccessController.doPrivileged(Native Method){}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:362){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:351){}}}{{{}at
org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289){}}}{{{}Caused by:
java.lang.ClassNotFoundException:
org.apache.nifi.security.util.TlsConfiguration{}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:387){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
[jira] [Created] (NIFI-9525) RPM build does not produce working Nifi
Gregory M. Foreman created NIFI-9525:
Summary: RPM build does not produce working Nifi
Key: NIFI-9525
URL: https://issues.apache.org/jira/browse/NIFI-9525
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 1.15.1
Environment: Centos 7
Reporter: Gregory M. Foreman
Maven RPM build fails to produce an operational Nifi installation.
{{{}$ mvn -version{}}}{{{}Apache Maven 3.8.4
(9b656c72d54e5bacbed989b64718c159fe39b537){}}}{{{}Maven home:
/opt/maven{}}}{{{}Java version: 1.8.0_312, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre{}}}{{{}Default
locale: en_US, platform encoding: UTF-8{}}}{{{}OS name: "linux", version:
"3.10.0-1160.49.1.el7.x86_64", arch: "amd64", family: "unix"{}}}
{{$ mvn clean install -Prpm -DskipTests}}
{{$ yum localinstall
nifi-assembly/target/rpm/nifi-bin/RPMS/noarch/nifi-1.15.1-1.el7.noarch.rpm}}
{{{}$ /opt/nifi/nifi-1.15.1/bin/nifi.sh start{}}}{{{}nifi.sh: JAVA_HOME not
set; results may vary{}}}
{{Java home: }}{{NiFi home: /opt/nifi/nifi-1.15.1}}
{{Bootstrap Config File: /opt/nifi/nifi-1.15.1/conf/bootstrap.conf}}
{{{}Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/nifi/security/util/TlsConfiguration{}}}{{{}at
java.lang.ClassLoader.defineClass1(Native Method){}}}{{{}at
java.lang.ClassLoader.defineClass(ClassLoader.java:756){}}}{{{}at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142){}}}{{{}at
java.net.URLClassLoader.defineClass(URLClassLoader.java:473){}}}{{{}at
java.net.URLClassLoader.access$100(URLClassLoader.java:74){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:369){}}}{{{}at
java.net.URLClassLoader$1.run(URLClassLoader.java:363){}}}{{{}at
java.security.AccessController.doPrivileged(Native Method){}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:362){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:351){}}}{{{}at
org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:124){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1247){}}}{{{}at
org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:289){}}}{{{}Caused by:
java.lang.ClassNotFoundException:
org.apache.nifi.security.util.TlsConfiguration{}}}{{{}at
java.net.URLClassLoader.findClass(URLClassLoader.java:387){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:418){}}}{{{}at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352){}}}{{{}at
java.lang.ClassLoader.loadClass(ClassLoader.java:351){}}}{{{}... 15 more{}}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (NIFI-1069) Nifi Service Status return 0 when service not running
[ https://issues.apache.org/jira/browse/NIFI-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972584#comment-16972584 ] Gregory M. Foreman commented on NIFI-1069: -- This issue still exists in Nifi 1.9.2. > Nifi Service Status return 0 when service not running > - > > Key: NIFI-1069 > URL: https://issues.apache.org/jira/browse/NIFI-1069 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 0.3.0 > Environment: CentOS 6.7 >Reporter: Andy Kruth >Assignee: Andre F de Miranda >Priority: Minor > Fix For: 1.1.0 > > > After successfully installing Nifi as a service with the following command: > sudo /opt/nifi-0.3.0/bin/nifi.sh install > running service nifi status has a return code of 0. > According to > http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html > if the service is not running then status should return 3. > This is not a major issue, you can still start and stop the service just > fine, but when using an idempotent tool like Ansible you cannot start the > service because the return code of status says the service is already started. -- This message was sent by Atlassian Jira (v8.3.4#803005)
