[
https://issues.apache.org/jira/browse/NIFI-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075380#comment-16075380
]
ASF GitHub Bot commented on NIFI-4153:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/1980
NIFI-4153: Use a LinkedBlockingQueue instead of a SynchronousQueue fo…
…r Request Replicator's thread pool so that requests will queue when all
threads are active, instead of throwing an Exception
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Is your initial contribution a single, squashed commit?
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-4153
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1980.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1980
----
commit 9d3a7618395e78246a43a90ba479b3e47450fb19
Author: Mark Payne <[email protected]>
Date: 2017-07-05T20:35:04Z
NIFI-4153: Use a LinkedBlockingQueue instead of a SynchronousQueue for
Request Replicator's thread pool so that requests will queue when all threads
are active, instead of throwing an Exception
----
> Site-to-Site causing "There are too many outstanding HTTP requests" error
> message
> ---------------------------------------------------------------------------------
>
> Key: NIFI-4153
> URL: https://issues.apache.org/jira/browse/NIFI-4153
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 1.4.0
>
>
> When using site-to-site in cluster, we sometimes see the following error
> message showing up in the log:
> {code}
> 2017-07-05 16:11:12,452 INFO [NiFi Web Server-318]
> o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException:
> There are too many outstanding HTTP requests with a total 100 outstanding
> requests. Returning Conflict response.
> {code}
> Once this occurs, it keeps occurring, sometimes making the UI unusable until
> the nodes are restarted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
