Thanks David,
Really appreciate it.
It clarified everything.
On Fri, 14 Jan 2022, 12:40 am David Handermann,
wrote:
> Hi Sanjeet,
>
> That's correct. Setting the JVM arguments for proxy server access can
> create the problems you observed, and it is unlikely to work as expected
> when it comes
Hi Sanjeet,
That's correct. Setting the JVM arguments for proxy server access can
create the problems you observed, and it is unlikely to work as expected
when it comes to proxy access. Various NiFi components use different
methods for creating network connections. For this reason, enabling
out
Thanks a lot for the quick response.
So u r suggesting we should not use proxy in jvm argument(nifi
bootstrap.conf file) lable also as it will impact other component.like in
my case its impacting nifi-api.
Regards,
Sanjeet
On Fri, 14 Jan 2022, 12:19 am David Handermann,
wrote:
> Hi Sanjeet,
>
Hi Sanjeet,
Thank you for providing the stack trace and details of your configuration.
Setting Java System properties in custom code is not a safe or supported
operation in NiFi. As you have observed, setting system properties alters
the behavior of other components, leading to unexpected results
Hi,
I encounter one "java.net.NoRouteToHostException: No route to host (Host
unreachable)" in *Nifi UI login page *.
The after debugging i realised when i am setting the proxy & port in
*System.setProperty("proxy address") & System.setProperty("port address") *in
my custom processor. then this
