Jim, You likely have a path through your flow where you are receiving an HTTP Request via HandleHttpRequest but you never respond via a HandleHttpResponse. When using these processors, it's important that every incoming FlowFile go to a HandleHttpResponse processor. Do you have some path in your flow where you are not responding to the request?
Thanks -Mark > On Feb 22, 2017, at 9:58 AM, James McMahon <[email protected]> wrote: > > I am getting the following errors when my users attempt to use curl or python > to post to my HandleHttpRequest processor (cannot export actual messages, > must select pieces and retype here): > WARNING > Received request from [IP address is here] but could not process it because > too many requests are already outstaning; responding with SERVICE_UNAVAILABLE > ERROR > ...claim=StandardContentClaim.... > transfer relationship not specified > > None of my apps can post to NiFi. > > I have a StandradSSLContextService and a standradHttpContextMap, both of > which are enabled. I suspect I may have inadvertently caused this problem by > setting my ContextMap parameters badly. Here are those params: > Maximum Outstanding Requests: 10000 > Request Expiration 10 min > > I've looked across my workflow and no flowfiles are queued up. So my > expectation is that there should be ample space in my ContextMap. But these > errors indicate otherwise. How do I fix this? > Thanks very much in advance for your help. > Jim
