For future reference, any setting that can be configured via the UI can also be
configured via the API. You can check the API Guide [1], but the simplest
method is to use the Developer Tools in your browser to record the API calls
executed when you perform the desired action through the UI and
Actually I just realized that the settings for the StandardHttpContextMap are
in my template so I can set the Request Expiration value there.
I have already automated the deployment of my template so the change to value
happens when I redeploy.
From: William Gosse
Sent: Wednesday, May 29,
Is there a way to set the StandardHttpContextMap Request Expiration value other
than through the GUI?
Can it be set through a configuration file or by the restful API?
This sounds a lot like what I'm experiencing:
http://mail-archives.apache.org/mod_mbox/nifi-issues/201808.mbox/%3cjira.13179212.1534379379000.90358.1534379760...@atlassian.jira%3E
I don't quite have the volumes but it's the same symptoms.
From: William Gosse
Sent: Saturday, May 25, 2019 12:22
I should mention that I'm on Nifi 1.9.2
From: William Gosse
Sent: Wednesday, May 29, 2019 4:04 PM
To: users@nifi.apache.org
Subject: RE: 503 Service Unavailable - Jetty Server
This sounds a lot like what I'm experiencing:
