We're updating the issue view to help you get more done. 

ScheduledTasks can burn up TCP connections

Description

In windows there is an outgoing TCP connection limit of 5000 (though configurable)

We have a server with many instances of our application on it. It is a beefy server and it can handle it in terms of resources.

Our application sometimes have a scheduled task that we run every 30 seconds. Sometimes when our servers are some load those scheduled tasks get a little bit behind, meaning a scheduled task starts when the last one isn't finished, and when the conditions are just right our server uses all 5000 connections and most things do not work. Upon investigation we find that many of the connections are scheduled tasks getting behind.

We have a fix that has prevents lucee's scheduled tasks from starting when the scheduled task is already running, Obviously, this isn't the only thing we changed to improve the stability of our app, but we feel this (or something like it) is a good change. I am logging the issue so you are aware, and hope you would consider the pending pull request.

Environment

windows server 2012 R2

Status

Assignee

Michael Offner

Reporter

Colby Litnak

Sprint

None

Fix versions

Affects versions

4.5.2.010

Priority

Critical