Hi all,

We are having trouble with a rather strange problem within our Schedulers. On our server we have 4 Scheduler instances running simultaneously. The last few weeks some tasks that are scheduled were not started, and in the log these tasks do not appear at all.

Last week we thought we discovered a pattern in this problem. As we schedule many tasks rapidly after each other, the queue builds up. I think that when Omniscope is using a lot of RAM, this queue is forgotten. Another plausible reason could be that “garbage collection” or “diagnostics ”actions also delete this queue.

The problem is that we cannot recreate the situation, but when it happens, this problem obviously disturbs our processes.

We solved the problem in one particular situation by leaving more time between the different tasks in order to avoid accumulating a queue of undone tasks.

Hope you guys can explain how the queue works and what reasons could be causing this problem? Thanks!