Re: Mysterious TIMEOUT

[Michael Moser]

LC,

You should be able to locate the StandardHttpContextMap controller
service using the Search function of the NiFi graph by searching
for df493519-0195-1000-fa60-52704d203613.  Once you locate that controller
service, its Settings tab will show you the processors that are currently
using that StandardHttpContextMap.  Your error message indicates a
HandleHttpRequest processor received a request, but the flowfile
containing that request never made it to a HandleHttpResponse processor to
send a response to the originator.

Hope this helps,
-- Mike


On Mon, Jul 7, 2025 at 12:15 PM Luis Carmona 
wrote:

> Hi there,
>
> I have a nifi flow working well, but I receive a warning  that I haven't
> been able to find out where it comes from. It says:
>
>
>- 12:07:04 CLT
>WARNING
>df493519-0195-1000-fa60-52704d203613
>
> 
>
>StandardHttpContextMap[id=df493519-0195-1000-fa60-52704d203613] Request 
> from 127.0.0.1 timed out; responding with SERVICE_UNAVAILABLE
>
>
>
> If I understand right it is saying the flow is answering timeout to the
> the peer about its initial http request.
>
> The questions would be:
>
> - Am I understanding properly the warning message ?
>
> - Is there a way to get more info about which flowfile, which processor
> are involved ?
>
>
> Thanks in advance
>
> LC
>
>
>

Mysterious TIMEOUT

[Luis Carmona]

Hi there,

I have a nifi flow working well, but I receive a warning  that I haven't 
been able to find out where it comes from. It says:


 *
   12:07:04 CLT
   WARNING
   df493519-0195-1000-fa60-52704d203613
   


   StandardHttpContextMap[id=df493519-0195-1000-fa60-52704d203613] Request from 
127.0.0.1 timed out; responding with SERVICE_UNAVAILABLE


If I understand right it is saying the flow is answering timeout to the 
the peer about its initial http request.


The questions would be:

- Am I understanding properly the warning message ?

- Is there a way to get more info about which flowfile, which processor 
are involved ?



Thanks in advance

LC