Thank you Mark. I saw that config parm and have been running with "Request
Expiration" set to 10 min. Based on the behavior I've observed, it buys me
time plus a large margin before the request times out with a "500: Service
Unavailable". It does not seem to restrict me to 10 minutes if I have a
Jim,
When you configure your HandleHttpRequest processor, there is a property for
the HttpContextMap to use.
Within the Standard Http Context Map you can configure a property named
"Request Expiration". By default,
it is set to 1 minute. If any request is not handled within that time limit, it
During this time when some of the steps are stopped, could just
connect your HandleHttpRequest to a different path through the flow
that returns an unavailable, and then when everything is back to
normal connect it back to the regular path?
On Mon, Feb 13, 2017 at 8:15 AM, James McMahon
Hello,
I'm not sure I fully understand the question...
You would need HandletHttpRequest -> some processors ->
HandleHttpResponse all in a running state in order for someone to
receive a response.
Can you elaborate on what you are trying to do?
Thanks,
Bryan
On Thu, Feb 9, 2017 at 4:32 AM,
Good morning. The first processor in my workflow is a HandleHttpRequest.
How do we set up to send a HandleHttpResponse if that processor is stopped
and so not in a running state?
Thank you. -Jim Mc.
