|
|
Open source tools written in Java. Sponsored by Acelet corporation |
| |Home | Products | Documents | Downloads | Partners | Contact | |
FAQ For SuperScheduler
For EJB (Poke) tasks, do I need to make the job file available on every node of the network?
No.
For EJB (Poke) jobs: SuperScheduler will save a private copy of the file with it. The original file is not needed for execution. If you modify the original file, the changes will not be carried to this task after the task is created.
I have Doer A and B. I start A before B. Will Doer A do most of the tasks?
Not necessarily. A and B compete equally.
Your network clock must be synchronized. The tolerance of the synchronized clock is about 10 milliseconds. The machine with the faster clock and fast network access will be more likely to be the early bird which catches the worm. There are other factors. For example, if machine A is busy swapping, A may be late. If A is with heavy load, it may be late.
When will holiday changes take effect?
It will take effect promptly (in interval: default is 2 seconds) for all tasks on all machines. But the already started task will not be affected.
Can I schedule tasks from C/C++ programs?
Yes. You can schedule tasks from any program written in any language. We recommend that you use SuperScheduler to set a task visually, than activate the task in your C/C++ by inserting a row in task database.
Can I schedule C/C++ programs as SuperScheduler tasks?
Yes. Any program written in any language can be scheduled, as long as the job can be run from operating system prompt. You schedule them as Operating System jobs.
How to construct a composite task?
You must create member tasks first. The member tasks can have any schedule terms (for example, every day or every month...). But the composite task ignores member task's term and runs at the scheduled time for a composite task. The member tasks can be scheduled independently. The member tasks can be Standby or even Suspended.
What are the differences between Suspended and Standby?
A Suspended task was created as a regular task with normal term (for example, run on every Friday with holiday policy). When you bring it back to active, you do not need to reset its term.
A Standby task is created to run by instructions, not by schedule. When you want to convert it to a normal task, you must specify a term.
Both Suspended and Standby tasks can be run by manually click. Standby can be run by programmatic call or be a member of a composite task. Support to run Suspended by programmatic call is Deprecated.
I have an Operating System task which requires a password as an command option. I do not want the password appear on the brief information. What should I do?
You can write a simple "wrapper" script or batch file with the password in it. The script or batch file is saved in a secure directory so unauthorized uses can execute it but can not read it. Then schedule this "wrapper" task.
I can not see correct result on History Task Panel or Log Task Panel. Why?
The common problems are:
When I click on the Run button, nothing happens. Why?
There should be a pop-up message window asking you to confirm your request. If you answer Yes and nothing happens, you probably run SuperScheduler Talker, not Doer. And at that time, there is no any Doer running at all. The Run button does not really run anything, but sends a request to Doers.
Anything I should know about scheduling Stateful Session Bean?
For Stateful Session Bean, one bean instance on the J2EE application server corresponds to one instance of interaction with a particular client (SuperScheduler).
The instance of the Stateful Session Bean may disappear by many reasons in a scheduled period, for example, it may be timeouted. When that happens, SuperScheduler will create a new instance of the Stateful Session Bean. But the state of the new created bean may or may not be the same as the deceased one. This scenario happens more often if the scheduled period is long. On the other hand, there may be many instances of SuperScheduler running as well. So you need to make sure the state of the Stateful Session Bean is what you expected.
How to bring a Suspended task back to Active?
Click the Activate button or Edit button on the Organizer Panel and click on the Ok button.
What should I do if the Status of a task is Error?
If you use SuperLogging as the logging system for SuperScheduler, you can go to the main menu > SuperScheduler > History > select Log > give a period > Log to view information about the error. Correct it, then open the Organizer Panel by either
Then highlight the task, click on Edit button. The Task Panel will open. Check all values and click on the Ok button.
What are Servlet or JSP jobs for?
SuperScheduler can schedule Servlet/JSP jobs. It is designed for procedural servlets or JSPs: the servlet or JSP are just "wrappers" for background procedures.
How many tasks can I schedule to run at the same time?
SuperScheduler does not set limitation on number of tasks. You run out your computing resources before running out numbers. In case you do find the starting process is slow, you can always add another Doer. The added Doer will take some load from existing Doers.
The answer to this question depends on your hardware and your tasks. We successfully tested 20 tasks running every minute on a small configuration. The testing environment is:
The overhead of starting a task is low.
Can I programmatically create tasks?
We encourage you to manually, visually create tasks using GUI tools of SuperScheduler. Then use SchedulerControl to manage tasks. SchedulerControl is very simple and easy to use. You have few chances to make mistakes.
It is error-prone for programmatically creating tasks and it is very difficult to test.
How do you terminate an Operating System script and signal error?
If you write an Operating System script (batch file) as an Operating System job for SuperScheduler/SuperWatchdog, you can terminate your script by calling
exit <exit_code>
You can find detailed information from your Operating System:
For Unix: man exit.
For Windows: go to Windows' help system and search for "exit code".
When I kill a task, I see "1;" as the result. Where does it come from?
That is the exit code from the task. When a task is killed, SuperScheduler gets all information available and shows it as result.
When a task fails, there is no email sent out. Why?
You need to check your settings:
1. Go to the SuperScheduler or SuperWatchdog window. Highlight the task in question. Click on the Edit button to open the Task Panel. The Alarm Email should be set correctly as the target email address.
2. Go to the main menu > System > Mail server to open the Mail Server Panel. Mail server must be specified correctly.
Is there a way to run a task by inserting a row in the task database?
Yes. But you should call API of SuperScheduler instead. If, by any reason, you need to access database directly, please contact us.
How can I find out when the SuperScheduler was started and when it was shutdown?
Read the output file. Search for words "starting", "shutdown", "exit" and "quit". It may be recorded even you press Control-c. But if the computer was power off, there would be no chance to record anything.