We are in webMethods 71 platform and we have a schedule task that runs twice in a day at specific time say at 12:15 PM and 16:15 PM. But we observe that the scheduler gets kicked off a minute or 2 minutes later.
Our interface is heavily dependent on the timing. Any idea about the scheduler behavior? Is there any fix?
Thanks
Meena
The scheduler manager uses JVM threads to execute tasks. It competes with every other thread in the JVM for CPU time. If the IS is fairly busy at these times then delays will occur.
If timing is critical, you may want to move the time sensitive components to their own IS instance.
Are you able to resolve the issue?
Wm Scheuler is always tricky beacuse it looks for threads available in IS instance so if timing is really important and your allocated thread count on IS is not sufficient, I would suggest to use third party tool like Tivoli for scheduling.
-nD
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.