PM
Subject Re: Issue with ExecuteAndWait when using Spring Session (Redis)
Depending on your deployment architecture, this exec and wait may no longer be the right
strategy. Yes, by managing the executor pool you can bound how many non-http-serving
threads (jobs) are executing concurrently
Depending on your deployment architecture, this exec and wait may no longer be
the right strategy. Yes, by managing the executor pool you can bound how many
non-http-serving threads (jobs) are executing concurrently on your web server's
host, but it is all premised on using your own hardware.
If it runs again then look at the logic where it's gotta decide whether this is
the initial call or if the job is already running and this is just a status
check. Is it looking at the request to figure that out? If so, and the
expected info isn't found, walk the data path to figure out where i
3 matches
Mail list logo
