3.6.4 and Job Queue problems

Since upgrading to 3.6.4, we've been having Job Queue Problems We have our queues set to 1 so only 1 job runs at a time. Scripts will retry if cannot make it into queue. Problem is, we are getting the "reaching max" error and the job never runs.

Second issue is we cannot update the job queue through the web. If I try, get message "Alert Recipient address may not be blank when alert options is selected". Does matter if the Alert Option is selected or not, still get this error. I tried to enter the Recipient Address, but still get same message. Web Version is 4.3 Build 282.

Looking for response so we can make a decision to go to next level or not.

Sorry. We either somehow overlooked the original post or the response didn't get through. I suspect the last.

Anyway, setting max queue size limit to 1 doesn't make sense. The queue would be unable to add new jobs if anything is already there, and you would get unnecessary errors.

In fact, the queue size is irrelevant in this situation. You need to set the job run-time mode to synchronous - uncheck asynchronous job property. The queue will take care of the rest.

In regard to "Alert Recipient address may not be blank when alert options is selected", I'll need to install this build on a test system and take a look.

Thanks for the info. I inherited the settings so don't know where they originally came from. I think the original thought was to only run one job in queue at a time. The jobs are set to retry if they don't make it into the queue the first time.

It should let you add 1 to the queue if the queue max is one. In this case, 1 meets the max and is not over the max. We can bump up to 2 if that was the only issue, but due to other errors, I'm thinking something ain't quite right.

Queue size is used to control run-away jobs and deal with jobs getting stuck in queue. The synchronous mode makes jobs to run sequentially, in other words, one job is run in a queue at any given moment in time. The asynchronous mode makes jobs to run in the background (chaos) and free the queue for running other jobs. Hope this helps.

Have you been able to test the Job Queue problem where it asks for a recipient for email notification whether you select for notification or not?

Not yet. This may take a little while.

In case you need to change it urgently, please use the scheduler's GUI interface, or just change the preferences.xml file manually.

Best regards, SysOp

This appears to be a browser compatibility issue leading to erroneous warning message. To fix this issue, please locate queue_edit.jsp file in the tools subfolder of the web console installation folder.
Open this file in any text editor.
Search for if (del_space(varform.maxjobs.value) == '') string.
Above that line insert if (!varform.sendalert.checked) varform.sendalert.value='N';
Save changes. This should fix the erroneous message and allow you to save queue configuration changes.