Learn, Share, Build

Java based web application on a tomcat server with Oracle DB and AngularJS front end.

Some of the oracle procs initiated through the UI can take 20+ mins to complete. For arguments sake, let's assume that a fire and forget approach is not suitable for what we are trying to do.

I've built a web service that simply calls Thread.sleep() to simulate a long running process. The connection abort time seems arbitrary.

Internet explorer 11 connection abort times: 
120 seconds
539 seconds
179 seconds

My question is, assuming our users will be using Internet Explorer 11 and we can't have them change their registry settings to force a longer keep-alive connection, what options do we have in the code base / tomcat server config to prevent a users connection from timing out during a long running process?