Hi Luis,
Thanks for reporting this problem and providing the background
details. This is a known issue related to applying FlowFile attributes
with the failure relationship, and it is being tracked in the follow
Jira issue:
https://issues.apache.org/jira/browse/NIFI-13324
Regards,
David
The Apache NiFi Team is pleased to announce the release of Apache NiFi 2.0.0-M3.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute data.
https://nifi.apache.org
The release artifacts can be downloaded from the project website.
. If it is
not on their roadmap, evaluating the effort for a direct implementation in
NiFi could be considered.
Regards,
David Handermann
On Wed, May 8, 2024 at 3:24 PM Brant Gardner
wrote:
> Hi David,
>
>
>
> Sure, we examined the 3.1.1 source code for spring-vault on GitHub and
> conf
.
Regards,
David Handermann
On Wed, May 8, 2024 at 2:26 PM Brant Gardner
wrote:
> Right, which is the one making us sad. :P
>
>
>
> *Brant Gardner*
>
> Software Developer – BI & Analytics
>
> Time: GMT -6:00
>
> bcgard...@solventum.com
> [image: A blac
is frequent, a network packet monitor such as tcpdump
[1] is one tool for evaluating network communication.
Regards,
David Handermann
[1] https://www.tcpdump.org/
On Fri, Mar 29, 2024 at 8:44 AM Shamsudeen Jameer
wrote:
>
> Hi David,
> Thanks for the information. I'm actually using the
recent version of NiFi would be a useful step, regardless of the
protocol used.
Regards,
David Handermann
[1] https://opentelemetry.io/docs/specs/otel/logs/
[2]
https://exceptionfactory.com/posts/2024/02/26/building-opentelemetry-collection-in-apache-nifi-with-netty/
On Thu, Mar 28, 2024 at 9:03
for comparison.
See the Proxy Configuration section of the Admin Guide for more details:
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#proxy_configuration
Regards,
David Handermann
On Mon, Mar 4, 2024 at 7:14 PM DC Gong wrote:
> Hi guys.
>
> I solved and share my sto
-authentication/
It is difficult to determine the problem based on the logs provided. As a
next step, enabling debug logging for the org.springframework.security
logger should provide additional details about the SAML handshake process.
Regards,
David Handermann
On Wed, Feb 28, 2024 at 9:25 PM DC
The Apache NiFi Team is pleased to announce the release of Apache NiFi 2.0.0-M2.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute data.
https://nifi.apache.org
The release artifacts can be downloaded from the project website.
documentation, but as with the project itself, the website is open for
collaborative input through Jira [1] and GitHub [2].
Regards,
David Handermann
Apache NiFi PMC Member
[1] https://issues.apache.org/jira/browse/NIFI
[2] https://github.com/apache/nifi-site
using
an IP address. Using a hostname or DNS name will avoid the SNI error and
allow standard TLS negotiation to work.
Regards,
David Handermann
On Thu, Nov 30, 2023 at 12:07 AM Ben .T.George
wrote:
> HI,
>
> Thanks for the update, i have changed and started the process, now the
&g
m/XrMcV3qs
>
> and my configuration:
> nifi.properties : https://pastebin.com/LeRMf9CS
>
> Regards
> Ben
>
>
>
> On Thu, Nov 30, 2023 at 8:28 AM Ben .T.George
> wrote:
>
>> HI,
>>
>> Thanks for the update, I will try to do it in that way.
&
into any other upgrade issues, please pass along the details.
Regards,
David Handermann
[1] https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
On Tue, Nov 28, 2023 at 4:12 AM Ben .T.George wrote:
>
> HI,
>
> How can I upgrade from 1.24.0 to 2.0.0-M1.
>
> I did
Affected versions:
- Apache NiFi 0.7.0 through 1.23.2
Description:
Apache NiFi 0.7.0 through 1.23.2 include the JoltTransformJSON Processor, which
provides an advanced configuration user interface that is vulnerable to
DOM-based cross-site scripting. If an authenticated user, who is
The Apache NiFi Team is pleased to announce the release of Apache NiFi 2.0.0-M1.
Version 2.0.0-M1 is the initial milestone release version of Apache NiFi 2.0.0.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute
data.
https://nifi.apache.org
The release
, which probably should be deprecated for removal in the next
major release version.
Regards,
David Handermann
On Mon, Sep 25, 2023, 8:24 AM Joe Witt wrote:
> Jim
>
> I don't really recall the history of that specific processor but what it
> can handle is just a function of what
.
Regards,
David Handermann
On Tue, Sep 19, 2023 at 3:45 PM Chris Sampson
wrote:
> Probably worth noting that the Jackson ObjectMapper is used in lots of
> places across the code base - 182 hits in GitHub on current main branch
> (some of those are duplicates within classes).
>
&
The Apache NiFi Team is pleased to announce the release of Apache NiFi 1.23.2.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute data.
https://nifi.apache.org
The release artifacts can be downloaded from the project website.
Severity: moderate
Affected versions:
- Apache NiFi 1.21.0 through 1.23.0
Description:
Apache NiFi 1.21.0 through 1.23.0 support JDBC and JNDI JMS access in several
Processors and Controller Services with connection URL validation that does not
provide sufficient protection against crafted
The Apache NiFi team is pleased to announce the release of Apache NiFi 1.23.1.
Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute
data. Apache NiFi was made for dataflow. It supports highly
configurable directed graphs
of data routing, transformation, and
ome
Processors use direct byte buffers, others do not, so it depends on the
supporting libraries used.
That's a longer way of saying, Joe's suggestion of 2 GB for maximum heap
size should be a safe starting point with 8 GB as the memory limit to avoid
OOM killed pods.
Regards,
David Handermann
On
versions using the jdk.tls.disabledAlgorithms property.
It is possible that a custom java.security configuration disabled TLSv1.3,
perhaps for compatibility reasons. Checking the java.security configuration
for the JDK installation would be a good next step for troubleshooting.
Regards,
David
Severity: moderate
Affected versions:
- Apache NiFi 0.0.2 through 1.22.0
Description:
Apache NiFi 0.0.2 through 1.22.0 include Processors and Controller Services
that support HTTP URL references for retrieving drivers, which allows an
authenticated and authorized user to configure a location
Severity: important
Affected versions:
- Apache NiFi 0.0.2 through 1.21.0
Description:
The DBCPConnectionPool and HikariCPConnectionPool Controller Services in Apache
NiFi 0.0.2 through 1.21.0 allow an authenticated and authorized user to
configure a Database URL with the H2 driver that
, but it sounds like
something that could be evaluated for adjustment in Apache NiFi.
If you could write up the details in a Jira issue, that would help track
this for potential improvement.
Regards,
David Handermann
[1] https://issues.apache.org/jira/projects/COMPRESS/issues/COMPRESS-555
On Tue
Hi Rodney,
More recent versions of Apache NiFi include updated versions of many
libraries, including Apache Commons Text 1.10.0, which was upgraded under
NIFI-10648 [1] for NiFi 1.19.0.
The Apache NiFi Release Notes [2] is a good place to start when looking for
updates.
Regards,
David
.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-11156
On Wed, Mar 8, 2023 at 6:55 AM ta.fiat.belastingdienst.nl via users <
users@nifi.apache.org> wrote:
> Hello,
>
> Is there a reason that, from version 1.16 on, validateXML produces just
> "Val
issues, please pass along the details.
Regards,
David Handermann
On Fri, Feb 17, 2023 at 3:44 PM wrote:
> Hi David
>
>
>
> Thanks a lot for answering here in this topic.
>
>
>
> A few comments to your reply.
>
>
>
>- SSHD config and the
, having more SFTP
connections results in poor performance, so smaller numbers can be better.
Regards,
David Handermann
[1] https://linux.die.net/man/5/sshd_config
On Thu, Feb 16, 2023 at 1:33 AM wrote:
> Hi guys
>
>
>
> It was upgrade time again on our side, we just upgra
the UnpackContent Processor from the flow configuration should
allow everything else to work as expected.
Regards,
David Handermann
On Thu, Feb 9, 2023 at 7:57 AM Tom Horvath via users
wrote:
> Adam,
>
> Thanks for the quick response. I am having an issue getting this to work.
> Option 1 is
PRIVATE KEY-
I recommend checking the header and footer of the private key file.
Regards,
David Handermann
On Mon, Feb 6, 2023 at 1:08 AM Ben .T.George wrote:
>
> Hello,
>
> I was trying to use an RSA key to connect to a remote server in order to
> list SFTP files.
>
> I ha
disabling TLS_DHE cipher
suites due to the computational overhead of larger DH key sizes when using
those particular options.
Regards,
David Handermann
On Mon, Jan 9, 2023 at 11:57 AM Rodney Ziebol
wrote:
> We are still getting security violations on our Nifi instance. I have
> att
trace of the error associated with the
HTTPS hostname error, that might be helpful, but comparing the certificate
properties against the Hostname setting for PutSplunkHTTP should clarify
the problem.
Regards,
David Handermann
[1] https://issues.apache.org/jira/browse/NIFI-10730
[2]
https
that a component or feature is
targeted for removal in subsequent major releases. The component will
continue to function in minor releases to provide a migration path to
recommended alternatives.
Regards,
David Handermann
On Sun, Nov 13, 2022 at 10:24 AM Patrick Timmins wrote:
> Also, deprecated doesn't m
Jim,
You're welcome! Thanks for following up and confirming the solution, great
collaborative effort!
Regard,
David Handermann
On Tue, Nov 8, 2022, 7:25 PM James McMahon wrote:
> That was it. Adding the port to the docker run command proxy got me to the
> promised land. I was the
with the following Docker command:
docker exec -it nifi /bin/bash
Regards,
David Handermann
On Tue, Nov 8, 2022 at 7:09 PM Dmitry Stepanov wrote:
> Make sure you use your full domain name
> ec2-3-238-27-220.compute-1.amazonaws.com
> David shorten it in his code
>
> On November 8, 2022 5:5
>
> I also see that I had to add an exception to permit https. When I created
> the instance, I created my own pem key pair. It is not signed by any CA.
> For a self-signed key pair like this, do I need to install a key in my
> browser security store to avoid adding that exception?
&g
in the container logs:
docker logs nifi | grep Generated
Regards,
David Handermann
[1] https://hub.docker.com/r/apache/nifi
On Tue, Nov 8, 2022 at 4:00 PM James McMahon wrote:
> Hi and thank you, David and Dmitry. In my case I was following this
> example,
>
> https://joeygoksu.com/software
of NiFi and some additional details on the
nifi.web values from nifi.properties?
Regards,
David Handermann
On Tue, Nov 8, 2022 at 1:54 PM James McMahon wrote:
> Has anyone successfully configured NiFi on AWS, and accessed it from a
> browser on a Windows desktop? I’ve tried following a few
, and is it running in a
containerized environment, or directly on a server?
Regards,
David Handermann
On Thu, Oct 27, 2022 at 10:35 AM Tiago Luís Sebastião (DSI) <
tiago.luis.sebast...@cgd.pt> wrote:
> Hi all,
>
>
>
> I'm having the same “problem”.
>
> I upgraded nifi ve
://exceptionfactory.com/posts/2022/04/26/introducing-apache-nifi-http-request-logging/
Feel free to follow up if you have additional questions.
Regards,
David Handermann
On Wed, Oct 26, 2022 at 9:51 AM Shawn Weeks
wrote:
> I have a requirement to audit client ip addresses as they conn
the Sensitive Properties Key Algorithm. [3]
Feel free to follow up if you have additional questions.
Regards,
David Handermann
[1]
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#deprecation-logging
[2]
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#property
in the upstream SSHJ main branch, but the resolution for NiFi is
waiting on a new release of the library. This will definitely be
incorporated in upcoming releases, as timing allows.
Thanks again for your reply and community participation!
Regards,
David Handermann
[1] https://cwiki.apache.org/confluence
Thanks for reporting this issue Josef, and thanks Mark for outlining the
background and workaround steps.
I submitted the the following pull request to address the problem:
https://github.com/apache/nifi/pull/6524
Regards,
David Handermann
On Thu, Oct 13, 2022 at 8:04 AM Mark Payne wrote
the
StandardRestrictedSSLContextService to use PKCS12 instead of JKS for the
Key Store Type and Trust Store Type.
Regards,
David Handermann
On Thu, Jul 21, 2022 at 1:30 PM Russell Bateman
wrote:
> David,
>
> Sadly, this is my experience. "changeit" works for me. And I tr
confirming the password on both
files is a good next step.
Regards,
David Handermann
On Wed, Jul 20, 2022 at 5:30 PM Russell Bateman
wrote:
> I'm trying to set up TLS for a service using *InvokeHTTP* against an
> external-to-NiFi Tomcat-based service and I have conf
Hi Ren,
Can you provide the NiFi version and the full stack trace associated with
the error message? As far as the error itself, are you using a particular
type of property encryption, such as AES-GCM?
Regards,
David Handermann
On Sun, May 29, 2022 at 11:25 AM Renaisa 'Ren' Wahed <
renaisa
Sanjeet,
Thanks for the confirmation, glad to hear the workaround resolved the
problem!
I have created the following Jira issue to correct the protection scheme
resolver:
https://issues.apache.org/jira/browse/NIFI-9988
Regards,
David Handermann
On Wed, May 4, 2022 at 12:40 PM sanjeet rath
Hi Sanjeet,
Following up on my previous reply, the potential workaround would actually
require changing "aes/gcm/256" to "AES_GCM". I am looking into addressing
this problem in a Jira issue.
Regards,
David Handermann
On Wed, May 4, 2022 at 11:41 AM David Handermann <
exce
may need to be addressed in a Jira issue.
Regards,
David Handermann
On Wed, May 4, 2022 at 11:22 AM sanjeet rath wrote:
> Hi Isha,
>
> We are using same java instalation.
>
> Our java version is open idk 11.
>
> In the same system only we are able to encrypt aes/gcm/256 for our old
or a password?
Setting the log level to DEBUG for the net.schmizz.sshj logger should also
provide additional details.
Regards,
David Handermann
On Wed, May 4, 2022 at 2:46 AM Jens M. Kofoed
wrote:
> Hi
>
> After migrating out flow from a single instance running version 1.13.2 to
> a 3
, there should be no concerns related to Log4j 1 and
recent versions of NiFi.
As far as ZooKeeper itself, upgrading the client library version is
something that will be addressed as part of regular dependency upgrade
reviews.
Regards,
David Handermann
On Mon, May 2, 2022 at 9:56 AM Gregory M. Foreman
promoting it to the framework level, if there is value in a non-persistent
content repository going forward.
Regards,
David Handermann
[1]
https://github.com/apache/nifi/blob/main/nifi-stateless/nifi-stateless-bundle/nifi-stateless-engine/src/main/java/org/apache/nifi/stateless/repository
, and may
actually have a negative impact on overall behavior. Changing the S2S
communication from HTTP to RAW may help, as it avoids using threads from
the web server pool, but in any case, changing to use load-balanced
connections should provide better overall behavior.
Regards,
David Handermann
On Fri
of the fundamental aspects
of TLS communication security.
With that background, the potential solution depends on why InvokeHTTP
considers the certificate invalid.
Regards,
David Handermann
On Fri, Mar 4, 2022 at 6:59 AM Jean-Sebastien Vachon
wrote:
> Hi all,
>
> what is the best wa
from DoS Filter
The last issue is not yet part of a released version, but the other two are
resolved in NiFi 1.15.3.
Although upgrading and migrating to connection load balancing will take
some work, it is the best path forward to address the issues you observed.
Regards,
David Handermann
/*'
-Dnifi.properties.file.path=conf/nifi.properties
org.apache.nifi.authentication.single.user.command.SetSingleUserCredentials
username passwordpassword
Regards,
David Handermann
On Fri, Feb 18, 2022 at 6:14 AM Breno Cesar
wrote:
> Hi Milke,
>
> As far as i know no, you could try:
> - Use nifi
.
Regards,
David Handermann
On Fri, Feb 11, 2022 at 11:18 AM David Early
wrote:
> Hi all,
>
> We are trying to get site-to-site working between 2 NiFi instances
> )v1.15.1) using SSL and single-user-provider authentication.
>
> Systems are up, certs have been inserted into the trsu
to process the symlinked file as a
directory, causing the error. I have assigned NIFI-6699 and will plan on
submitting a pull request to resolve the problem soon.
Thanks again for reporting this issue and helping track down the problem!
Regards,
David Handermann
On Thu, Feb 3, 2022 at 10:58 AM Mark
, GetSFTP, or both processors.
Regards,
David Handermann
On Thu, Feb 3, 2022 at 9:57 AM Guillermo Muñoz Salgado
wrote:
> Hi all,
>
> We are developing a use case in which we have to get some files from a
> server. We have implemented it by the listSFTP + FetchSFTP way in a 3 nod
in light of recent improvements to the
framework.
Feel free to create a new issue and we can use that going forward.
Regards,
David Handermann
On Thu, Feb 3, 2022 at 12:23 AM Cannon Palms wrote:
> Thanks Joe! Do you know if there is an existing JIRA issue to track such a
> feature pr
configuration
explains why you might see other TLS handshakes indicating support, but not
handshakes initiated through InvokeHTTP.
Regards,
David Handermann
On Tue, Jan 25, 2022 at 12:19 PM Shawn Weeks
wrote:
> I need some help understanding how the InvokeHTTP processor negotiates
Mike,
You're welcome! The nifi-kite-bundle has been removed from the main branch
of Apache NiFi as of the following commit, so this shouldn't be a problem
for future builds.
https://github.com/apache/nifi/commit/8edb5faac9ff469e4c810891c30892962ed83b29
Regards,
David Handermann
On Wed, Jan 19
-core
Regards,
David Handermann
On Wed, Jan 19, 2022 at 8:27 AM Michal Tomaszewski <
michal.tomaszew...@cca.pl> wrote:
> Compilation with -Dhive.version=3.1.0 makes the problem.
> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> is not successful.
> We also tes
Gregory,
Thanks for the confirmation. So this issue is specific to the RPM build,
correct? NiFi starts correctly using the tar.gz binary?
Regards,
David Handermann
On Fri, Dec 17, 2021 at 2:23 PM Gregory M. Foreman <
gfore...@spinnerconsulting.com> wrote:
> David:
>
> No mod
Gregory,
Thanks for reporting this issue. Do you have any notification services
configured as part of the bootstrap.conf, such as the HTTP notification
service?
Regards,
David Handermann
On Fri, Dec 17, 2021 at 1:56 PM Gregory M. Foreman <
gfore...@spinnerconsulting.com> wrote:
> Hel
allow the
OIDC configuration to load as expected in NiFi 1.14.0.
Regards,
David Handermann
On Wed, Dec 8, 2021 at 4:54 AM Ganesh, B (Nokia - IN/Bangalore) <
b.gan...@nokia.com> wrote:
> Hi ,
>
>
>
> We are using apache nifi 1.14 . We have 3 nodes in nifi cluster , cluste
or not this issue is
resolved in 1.15.0 RC2.
Regards,
David Handermann
On Tue, Nov 2, 2021 at 9:00 AM Weiss, Christian
wrote:
> Hi guys,
>
>
>
> we did an upgrade to NiFi 1.14.0 from 1.11.4 and migrated some our Flows
> for testing.
>
> Unfortunately the FetchHDF
Thanks for providing the Java version details.
Only a small number of components use the NiFi SSLSocketChannel class,
which is why most components should not have any problems with TLS 1.3.
Updates to the Distributed Cache Server and Clients should resolve these
issues.
Regards,
David Handermann
Server as well, but there may be some
improvements that could be made to SSLSocketChannel as well.
If you could provide these details along with the Java version in a NiFi
Jira issue, that would be very helpful.
Regards,
David Handermann
On Thu, Sep 23, 2021 at 7:33 AM Shawn Weeks
wrote:
>
You're welcome, glad to hear that worked!
Regards,
David Handermann
On Mon, Aug 23, 2021 at 12:07 PM Mike Sofen
wrote:
> That was it – *setting the **nifi.web.proxy.host to the VM’s external IP*
> (and leaving the nifi.web.https.host blank) resulted in the Nifi login
> screen, and I
a reverse DNS lookup of the public IP address should return the
host value to use for that property, and for accessing NiFi through the
browser.
Regards,
David Handermann
On Mon, Aug 23, 2021 at 11:16 AM Mike Sofen
wrote:
> Hi David,
>
>
>
> Thanks for the tip to try a blank https h
/html/administration-guide.html#security_configuration
Regards,
David Handermann
On Mon, Aug 23, 2021 at 8:06 AM Mike Sofen
wrote:
> minor correction - the port shown (8543) was from the alternate port test,
> the regular port test 8443 returns a similar error:
> " Nifi fails to start
. The
Sensitive Properties Key can be specified using the following environment
variable when running in Docker: NIFI_SENSITIVE_PROPS_KEY. The value must
be the same on all clustered nodes.
Regards,
David Handermann
On Thu, Aug 5, 2021 at 6:20 AM Yildiray Kabak wrote:
> Dear all,
>
>
>
then
prompts for username and password authentication.
Regards,
David Handermann
On Tue, Aug 3, 2021 at 1:59 PM Mike Thomsen wrote:
> I built a fresh copy of 1.15.0-SNAPSHOT and got prompted for a cert
> when I hit the web console. It ultimately didn't block me from logging
> in
You're welcome Joe, that's great news!
Regards,
David Handermann
On Tue, Jul 20, 2021 at 2:28 PM Joe Obernberger <
joseph.obernber...@gmail.com> wrote:
> Success! Thank you David.
> Now I'm more confident to upgrade the entire cluster. Cheers!
>
> -Joe
> On 7/20/2021 3:08
and running the
set-sensitive-props-key command again? Make sure to have the PBE value set
for nifi.sensitive.props.algorithm.
Regards,
David Handermann
On Tue, Jul 20, 2021 at 1:59 PM Joe Obernberger <
joseph.obernber...@gmail.com> wrote:
> Hmm - with:
> nifi.sensitive.pro
algorithm in nifi.properties?
Regards,
David Handermann
On Tue, Jul 20, 2021 at 12:32 PM Joe Obernberger <
joseph.obernber...@gmail.com> wrote:
> Thank you David - your help is great!
>
> I've removed the 1.14.0 node from the cluster and it fires up OK without a
> flow file
key,
to ensure that all nodes share the same configuration.
Please pass along any stack traces if NiFi does not startup after making
those changes.
Regards,
David Handermann
On Tue, Jul 20, 2021 at 11:54 AM Joe Obernberger <
joseph.obernber...@gmail.com> wrote:
> Thank you David.
>
1.14.0 is only suitable for standalone
deployments. As a self-signed certificate, it is not intended to be used
for clustered configurations, so existing documentation on configuring a
secure cluster provides the recommended approach.
Regards,
David Handermann
On Tue, Jul 20, 2021 at 9:31 AM Joe
is preferred,
but it is possible to upgrade from 1.13.2 or earlier and continue using the
previous default of PBEWITHMD5AND256BITAES-CBC-OPENSSL.
Regards,
David Handermann
On Mon, Jul 19, 2021 at 4:09 PM Lipunov Aleksei
wrote:
> Hi,
> according to NIFI-8246 defaults are
&g
upgrading from an
existing flow.xml.gz, this property needs to be the exact same value used
prior to upgrading.
Can you try changing nifi.sensitive.props.algorithm to P
BEWITHMD5AND256BITAES-CBC-OPENSSL?
Regards,
David Handermann
On Mon, Jul 19, 2021 at 6:50 PM Joe Obernberger <
joseph.obern
library on the class path. When you upgraded, did you
clear out the "work" directory and can you confirm that there are no other
copies of version 1.13.2 JAR files in the "lib" directory?
Regards,
David Handermann
On Mon, Jul 19, 2021 at 8:10 AM Man on the Moon <
environment, that would help isolate the problem.
Regards,
David Handermann
On Tue, Jun 1, 2021 at 2:42 PM Robert R. Bruno wrote:
> We wanted to give you another data point. We tried 3.14.9 and 1.20 for
> the two libraries and no errors. Also, our services are http not https.
> Hope t
of the
equation. Java 11 supports TLS 1.3, whereas Java 8 did not support TLS 1.3
until more recent updates. It would be interesting to know if your
configuration still works with a more recent version of OkHttp in the 3.x
series. Thanks again for providing the feedback.
Regards,
David Handermann
timeout property would be useful.
Regards,
David Handermann
On Sun, May 30, 2021 at 4:54 AM Robert R. Bruno wrote:
> When seeing the error we put our timeouts values in the processor both to
> 5 mins as a test and still saw the errors and well before 5 minutes. We
> also slowed the proce
such as the number
of connections, payload sizes, network latency, or local resource
consumption.
Regards,
David Handermann
On Sat, May 29, 2021 at 2:08 PM Joe Witt wrote:
> K. We have seen specific jvm versions causing issues with socket
> handling. But had not seen it on Java 11 though may be po
/NIFI-6714
The message is a warning on Java 11, but does not prevent NiFi from
starting. Newer versions of Java block such illegal reflective access
operations, so for now, Java 8 or 11 should work.
Regards,
David Handermann
On Wed, May 5, 2021 at 10:22 AM Cristiano Silva
wrote:
> I use open
is occurring
as expected.
Regards,
David Handermann
On Mon, Mar 29, 2021 at 10:34 PM Rosso, Roland <
roland.ro...@adventhealth.com> wrote:
> Hi David,
>
>
>
> I use the nifi-toolkit to create the keystore and truststore to make sure
> clientAuth and se
es a PrivateKeyEntry
and not a TrustedCertEntry.
Regards,
David Handermann
On Mon, Mar 29, 2021 at 5:49 PM Rosso, Roland
wrote:
> I've tried this one more time (Nifi 1.12.1 to Registry 0.6.0).
> Re-signed/Re-imported the certs.
>
> The new "server" cert is of the type:
>
> Alias nam
at which the REST client connects,
this could be problematic, but it is one potential option.
Regards,
David Handermann
On Thu, Feb 4, 2021 at 8:50 AM Ralph Vercauteren wrote:
> Thanks, Chris,
>
> This is the same problem I figured,
>
> Is it possible to create an executeScrip
for delivery to the REST client.
Regards,
David Handermann
On Thu, Feb 4, 2021 at 7:47 AM Ralph Vercauteren wrote:
> Hi David,
>
> Thanks for responding.
>
> I understand that part, still have the issue to see how we get the kafka
> messages from a topic.
>
> [image: ima
for each one in order to determine the
optimal settings for your configuration.
Regards,
David Handermann
On Thu, Feb 4, 2021 at 3:32 AM Ralph Vercauteren wrote:
> Hi all,
>
> Not sure if I need to ask this in this mailing list or the list of the
> developers.
>
> I want to cr
pull/4557>, which has not yet been reviewed.
Please feel free to comment on the PR or the Jira issue
<https://issues.apache.org/jira/browse/NIFI-7836> if you have any thoughts
on the implementation or potential use cases.
Regards,
David Handermann
On Mon, Nov 30, 2020 at 11:03 AM Madhan Vishwas
Etienne,
No problem, I understand, it sounds like you are close to getting it
working. Feel free to follow up if you run into additional issues.
Regards,
David Handermann
On Wed, Nov 25, 2020 at 8:28 AM Etienne Jouvin
wrote:
> David.
>
> Did not have time this morning to test.
>
either on the LDAP server, or in the way NiFi is attempting to
query LDAP.
Regards,
David Handermann
On Wed, Nov 25, 2020 at 5:19 AM Etienne Jouvin
wrote:
> Just for information, did not have time to test it from now.
> I was not able to get this Walk Throughs documentation.
> htt
a null content
claim, resulting in the exceptions you reported.
I have created an issue in Jira outlining the problem (
https://issues.apache.org/jira/browse/NIFI-8024) and I will look at
implementing a solution soon.
Regards,
David Handermann
97 matches
Mail list logo
