3.6.2 windows version queue bug

Hi
Not sure if you've fixed this in a later release but we had a production incident arising from the creation of a queue yesterday. We created one using the remote control client and tried to set the "maximum number of queued jobs" slider to unlimited (0). It appeared to work but on save and scheduler restart the queue ended up reading 1 job allowed, and actually not allowing any jobs to queue in it. The jobs trying to run displayed the following message

3/05/2010 13:34:06:872 1 0 0 24x7 Scheduler Unable to add new job to the "XXXX" job queue. Maximum jobs in queue limit reached. Maximum allowed number: 1 jobs. 24x7 is waiting for currently running jobs to complete and make this queue available to new jobs.

and no jobs assigned to that queue actually ran.

We've set the queue to 250 max queued jobs and it seems to function, but it's still bad we can't use the unlimited setting and even worse that 1 doesn't actually work.

This has been fixed in 3.6.10, but that version hasn't been publicly released yet. We expect it to be available next week.

By the way, the bug is not specific to the remote control. It can be easily reproduced with the scheduler when running it in GUI mode. The Queue Properties dialog is supposed to allow choosing 0 for max jobs value which means "unlimited" number of jobs, but it caps the minimum to 1. If you select any positive value, everything is ok.