If this is just a one off/short term debugging thing I’ve found mitmproxy to be
helpful for this. If you configure it as the proxy it works as you’d expect.
-joey
On Nov 12, 2020, 8:53 AM -0800, Etienne Jouvin , wrote:
> Hello.
>
> InvokeHTTP is using OkHttpClient
> See on OkHttpClient the
Hello.
InvokeHTTP is using OkHttpClient
See on OkHttpClient the logging configuration.
But if it required to add an interceptor, it will not be easy.
But in the code, you will find something like :
private void logRequest(ComponentLog logger, Request request) {
That is the point, the logs don't show any error, the UI get stuck and then you
are kicked out:
[cid:02b59616-d7ae-4ca6-ad9b-83b2db8c0ca8]
about the 3 circles:
*The spinning wheel keeps going and I never get back the control, I
finally are kick out from the session.
*The request
Hi All!
I have to implement a flow with NiFi that involves consuming different AMQP
queues whose number may change in time.
One of the requirements is that when a new queue is available (of an old one is
no more available) the NiFi flow adjusts to the new situation without the need
for any
I'm trying to get a good look at the request that is being sent over.
Does anyone know what sort of logback configuration would work best
for showing the headers and the body being sent?
Thanks,
Mike
Hello,
Can you please share any errors from nifi-app.log or nifi-user.log
that correlate with your initialize error?
NiFi does not perform any retries in a loop when pulling from registry.
Thanks,
Bryan
On Wed, Nov 11, 2020 at 6:10 PM Luther Blisset wrote:
>
> Hi,
> I'm importing a PG from a
Hello,
This idea/problem has come up a few times. The issue is that if you allow
incoming connections with dynamic queue/topic on these "consume"
processors, then there is potentially an unbounded number of topics/queues
to consume from. How does the processor ever know to stop consuming from
one
