Requests for new connections are not satisfied by this application because the connection backlog limit has been exceeded. Also, the number of currently active connections is a high percentage of the high water mark for the number of currently active connections, indicating a spike in application workload. An application workload spike likely prevented the z/OS application from completing the workload. To determine this, the following metrics in the Connections table are monitored:
This situation occurs if the active connections value is greater than the value for 90% of the high water mark and the backlog connections rejected value is greater than 0 (zero). A workload spike is likely the cause of the z/OS application being unable to complete its workload.
To resolve this problem, increase the application backlog queue limit or create an additional instance of the application.
By default, this situation does not start automatically and must be manually started to run.