Hi, If I use the ProgressiveDisplay component to display a long running task later, it looks like the tomcat thread is not released back to its pool immediately so there may be less tomcat threads available then?
For example, from the extremely helpful jumpstart site, I can see the XHR call does not return immediately and waits 6 seconds: https://tapestry-jumpstart.org/jumpstart/examples/ajax/progressivedisplayvariations [cid:image001.png@01DB2C5F.9CE721B0] Tapestry has an interface to https://tapestry.apache.org/current/apidocs/org/apache/tapestry5/http/internal/AsyncRequestService.html which looks like it may be using the servlet 3’s asynchronous Servlet API requests but is an example of its use or some documentation on its use? Alternatively, another option is some kind of polling to keep checking when the long running process is ready so the tomcat thread isn’t held on? Are there any other approaches to this issue so the tomcat thread isn’t being held too long with a ProgressiveDisplay? Thanks, Niran Confidentiality note: This e-mail may contain confidential information from Clarivate. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this e-mail is strictly prohibited. If you have received this e-mail in error, please delete this e-mail and notify the sender as soon as possible.
