Versions Compared

Old Version 2

changes.mady.by.user Unknown User (dbranton)

Saved on

compared with

New Version 3

changes.mady.by.user IDERA

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Example thread pool backlog entries from an uptime.log file:

No Formatcode
2010-05-18 03:15:07,473 WARN (Launcher:117) - Thread pool backlog: Events in queue: 110 Available: 0 Busy:75
2010-05-18 03:15:07,474 WARN (Launcher:117) - Thread pool backlog: Events in queue: 111 Available: 0 Busy:75 
2010-05-18 03:15:07,474 WARN (Launcher:117) - Thread pool backlog: Events in queue: 112 Available: 0 Busy:75

...

There are various reasons why you may be seeing these messages:

  • The serviceThreads variable in the uptime.conf file is set to a higher value than the connectionPoolMaximum parameter.  Note that the connectionPoolMaximum value should be at least 10% higher than the serviceThreads value.

  • Your hardware platform is saturated and can't execute tasks quickly enough.
  • The average time required to complete a task is simply too long.  If you have many monitors that consistently fail or reach their timeout setting, this can substantially impact the up.time task list.  uptime Support can provide further information and guidance on how to improve task execution performance and optimize the size of your task list.