HTTPS 2-minute timeout?

I have a process that includes running complex server-side processing while a loading screen (or other screen) is displayed to the client. In a regular (HTTP) environment, this process can run several minutes with no timeouts. In an https environment, it dies with a 503 push to client after 2 minutes. The server.xml files look the same and I cannot locate the 2 minute timeout anywhere. My friend, Google, doesn’t have much to offer besides changing around the port numbers. 


Any ideas? I know this isn’t a solution, but I’ll post it on here as soon as I have one.



Found someone more knowledgeable than I (which is very easy to do). Turns out that the timeout had nothing to do with https. Rather it was tomcat worker timeout: Workers are used for load balancing between multiple tomcat instantiations.

Leave a Reply

Powered by

Up ↑

%d bloggers like this: