| Title | Excessive CPU usage when 0 tasks are scheduled |
| Date Updated | 12/21/2001 |
| Versions affected | Automize 4.0-4.21 & JavaScheduler 2.8-4.11. JavaScheduler is more prone to this problem. |
| OS affected | All |
| Description | JavaScheduler uses excessive CPU when 0 tasks are scheduled. Some systems are effected by this. Most systems show this behavour when the user has 1 task and then deletes this single task. |
| Causes | An internal error causes JavaScheduler to write continuously to the error logs. This increases the CPU usage. The problem generally goes away if the scheduler engine is restarted. |
| Solution | 1. Schedule a single dummy
task. 2. This issue has been resolved and is targeted for inclusion in the next update releases of JavaScheduler and Automize. |
| Output Log | Nothing |
| Debug Log | java.lang.ArrayIndexOutOfBoundsException:
0 >= 0 at java.util.Vector.elementAt(Unknown Source)at javax.swing.table.DefaultTableModel.setValueAt(Unknown Source) at AdminServer.parseMessage(AdminServer.java:121) at AdminServer.run(AdminServer.java:48) |